Skip to main content
​
Surface narrowed to search, answer, and context
The API surface is trimmed down to the capabilities that carry the product.Removed:
  • analyse — the POST /v1/analyse endpoint and the analyse MCP tool are gone. Rule evaluation over health records is no longer part of the knowledge layer.
  • The experimental knowledge-graph context endpoint (POST /v2/context) and its playground route are withdrawn. The stable POST /v1/context is unaffected and remains the supported way to get a patient-aware answer.
Unchanged: search, answer, and context keep their contracts on both REST and MCP. atb and drug stay on the roadmap.
​
Initial knowledge layer
First release of the Locus knowledge layer — REST + MCP over the shared clinical knowledge base.Capabilities (REST + MCP):
  • search — structured, citable retrieval.
  • answer — grounded, cited answers.
  • context — answer accounting for a coarse patient profile, with conflicts.
  • analyse — apply a clinical rule to inline health records, with sourced recommendations.
Platform:
  • Bearer lsk_… authentication against the shared key store.
  • MCP server over Streamable HTTP with curated tools and output schemas.
  • Auto-generated API reference with an interactive playground.
Roadmap: atb (deterministic antibiotic decision) and drug (BDPM medication data) are designed, not yet available.