atb (roadmap) - Locus

Not yet available. atb is designed but not implemented. There is no endpoint or MCP tool yet — this page describes the intended behavior so integrators can plan. It will appear in the API Reference and tools/list only once shipped.

What it will do

atb will provide a deterministic antibiotic decision (antibioclic-style) from a clinical situation — not an LLM guess. Given a situation, it returns either a decision or a request to enrich the profile.

The agentic pattern

When required information is missing, atb will not guess. It will return what is missing, so an agent can enrich the situation and call again:

situation ──▶ atb ──▶ decision
                 └──▶ "missing: <field>"  → agent enriches → atb again

This keeps the engine deterministic while staying usable inside an agent loop.

Intended shape (subject to change)

// Request
{ "situation": { /* clinical situation fields, TBD */ } }

// Response — either a decision…
{ "decision": { "antibiotic": "...", "dose": "...", "duration": "...", "rationale": "..." } }

// …or a request for more information
{ "needs": ["fonction rénale", "allergies"] }

The exact situation and decision contracts are being designed. This page will be replaced by the live reference when atb ships.