Skip to main content
Locus turns europeans clinical guidelines into a knowledge layer you can search, ask, and act on — from a web widget, a REST API, or an MCP server. All three surfaces sit on the same knowledge base and the same API keys. There is one engine; the surfaces are thin.

​
The three surfaces

Widget

A drop-in widget (embed + JWT) for end-user search inside a partner app such as an EHR. Front-end, prod-critical, unchanged by this API.

REST API

Canonical JSON endpoints for the six capabilities. Self-documenting via OpenAPI, with an interactive playground in this site.

MCP server

The same capabilities as curated tools for LLM agents, over Streamable HTTP.

​
The capabilities

search

Structured, citable units from the clinical knowledge base — never a blob.

answer

A concise, cited answer grounded only in the sources.

context

An answer that accounts for a coarse patient profile, surfacing conflicts.

analyse

Apply a clinical rule to health records and attach sourced recommendations.
atb (antibiotic decision) and drug (medication data) are on the roadmap — designed but not yet available.