> ## Documentation Index
> Fetch the complete documentation index at: https://docs.locusmedical.fr/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Medical knowledge layer — search, answer, and act on clinical guidelines via REST + MCP. 

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

<CardGroup cols={3}>
  <Card title="Widget" icon="window">
    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.
  </Card>

  <Card title="REST API" icon="code" href="/en/quickstart">
    Canonical JSON endpoints for every capability. Self-documenting via OpenAPI, with an interactive playground in this site.
  </Card>

  <Card title="MCP server" icon="robot" href="/en/mcp/overview">
    The same capabilities as curated tools for LLM agents, over Streamable HTTP.
  </Card>
</CardGroup>

## The capabilities

<CardGroup cols={2}>
  <Card title="search" icon="magnifying-glass" href="/en/capabilities/search">
    Structured, citable units from the clinical knowledge base — never a blob.
  </Card>

  <Card title="answer" icon="comment-medical" href="/en/capabilities/answer">
    A concise, cited answer grounded only in the sources.
  </Card>

  <Card title="context" icon="user-pen" href="/en/capabilities/context">
    An answer that accounts for a coarse patient profile, surfacing conflicts.
  </Card>
</CardGroup>

<Note>
  `atb` (antibiotic decision) and `drug` (medication data) are on the [roadmap](/en/roadmap/atb) — designed but not yet available.
</Note>