> ## 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.

# Capabilities overview

> The five Locus capabilities and when to reach for each.

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.

| Capability                          | Use it when you want…                         | Status    |
| ----------------------------------- | --------------------------------------------- | --------- |
| [search](/en/capabilities/search)   | structured, citable sources for a query       | Available |
| [answer](/en/capabilities/answer)   | a concise, cited answer                       | Available |
| [context](/en/capabilities/context) | an answer that accounts for a patient profile | Available |
| [atb](/en/roadmap/atb)              | a deterministic antibiotic decision           | Roadmap   |
| [drug](/en/roadmap/drug)            | structured medication data                    | Roadmap   |

## How they build on each other

```
search   ── retrieval foundation
  └── answer    = search + relevance ranking + answer composition
        └── context  = answer + coarse patient profile + conflicts
```

`search` is the foundation; `answer` and `context` call it internally. `atb` and
`drug` are independent engines (no retrieval dependency).

## Routing guidance

* A guideline / recommendation lookup → **search**, **answer**, or **context**.
* An antibiotic decision → **atb** (roadmap).
* A medication datum → **drug** (roadmap).