Build with AI tools
Give a coding assistant these docs in a form it reads well, so the code it writes uses the right model id, key header and reasoning field.
A coding assistant that has not read these docs writes OpenAI code. It sends an
OpenAI model name, reads only message.content, and drops Olive's reasoning.
Point it at one of the files below before it writes anything.
Files for assistants
| File | What it holds | Use it when |
|---|---|---|
/llms.txt | A short brief on the API, then a linked index of every page | The assistant can follow links and you want it to pick the pages it needs |
/llms-full.txt | Every page in one file, in sidebar order | You paste or attach one file and want the whole picture |
/llms.md/<page> | One page as Markdown. /quickstart is also at /llms.md/quickstart | You want one topic, such as streaming, without the rest |
Each file opens with the same brief: the bearer header, the model id
olive, the base URL, the reasoning_content field, the limits, and
what is not supported. Values are filled in, so the assistant never sees a
placeholder.
From a page
Every page has two buttons under its title.
- Copy Markdown copies the page as Markdown, ready to paste into a chat.
- Open sends the page to ChatGPT, Claude, Cursor or Scira AI, or shows it as plain Markdown.
A prompt that works
Paste this, with the full-text file attached or its URL given:
Read the Avey Olive docs in llms-full.txt before writing code.
Use the OpenAI SDK with the base URL, model id and bearer key it gives.
Print message.reasoning_content and message.content separately.
Read the key from the AVEY_API_KEY environment variable.Clinical review stays in
The brief tells assistants that Olive is a clinical model and that a qualified clinician reviews output before it reaches a care decision. If generated code sends Olive's answer straight to a patient, or to a decision with no review step, change it before you ship it.
Do not paste patient records into an assistant to build test prompts. Write synthetic cases.