Documentation, issued with your key.
API access is gated. Apply through the short form — if we can support the use case we provision a key, hand over the reference, and work through the integration with you directly.
/access
By application
- 01 · Apply
- Describe the use case and the clinical setting it runs in.
- 02 · Review
- We check it against Lor-1 intended use and the stated limits.
- 03 · Provision
- Key issued, reference and SDK examples sent with it.
- 04 · Integrate
- Direct line to the team through your first calls.
- Surface
- REST + streaming
- Compat
- OpenAI-shaped
- SDKs
- TypeScript · Python
- Access
- Approved integrators
Three sections, sent with the key.
03 sections
- 01
Quickstart
The first API call in under five minutes — curl, TypeScript, or Python. The endpoint is OpenAI-compatible, so pointing an existing SDK at it is a one-line change.
- 02
API reference
Every endpoint, parameter, and response shape — typed, example-covered, and paired with the Lor-1 system prompt contract.
- 03
Guides
Streaming, tool use, citation handling, structured extraction, safety guardrails, and the SA clinical prompt patterns we have settled on internally.
How access works
Building something clinical on Lor-1?
Tell us about the use case on the form. Clinical software teams, hospital IT, and healthtech builders get first priority.
Open the API access form