Skip to main content
Locus exposes its knowledge through a small set of capabilities. Each one is a single engine behind a thin REST route and a curated MCP tool — same behavior on both surfaces.
CapabilityUse it when you want…Status
searchstructured, citable sources for a queryAvailable
answera concise, cited answerAvailable
contextan answer that accounts for a patient profileAvailable
analyseto apply a clinical rule across health recordsAvailable
atba deterministic antibiotic decisionRoadmap
drugstructured medication dataRoadmap

​
How they build on each other

search   ── retrieval foundation
  └── answer    = search + relevance ranking + answer composition
        └── context  = answer + coarse patient profile + conflicts
        └── analyse  = rule → evaluate health records → answer per match
search is the foundation; answer, context, and analyse call it internally. atb and drug are independent engines (no retrieval dependency).

​
Routing guidance

  • A guideline / recommendation lookup → search, answer, or context.
  • A decision over patient health records against a rule → analyse.
  • An antibiotic decision → atb (roadmap).
  • A medication datum → drug (roadmap).