SimpleCompatibility and AI-readable docs
Supported V1 surface, machine-readable documentation, and boundaries.
SimpleLLM V1 implements an OpenAI-compatible inference surface. Compatibility describes specific endpoints and request formats, not every feature exposed by every OpenAI client.
Supported public routes
| Operation | Endpoint |
|---|---|
| Chat, streaming, model-dependent vision and tools | POST /v1/chat/completions |
| Model IDs | GET /v1/models |
| Speech generation | POST /v1/audio/speech |
| File transcription | POST /v1/audio/transcriptions |
| Image generation | POST /v1/images/generations |
| Rate-limit status | GET /v1/rate-limit |
| Account usage | GET /v1/usage |
| Read-only key metadata and usage | GET /v1/keys/ and documented subroutes |
Audio and image availability depends on the separately configured services. Listing chat models does not establish media-endpoint availability.
What is not included
POST /v1/completions is a 501 stub in V1; use Chat Completions. Responses, embeddings, batch jobs, direct OCR, voice cloning, voice design, and a voice-catalogue endpoint are not part of this documented V1 router.
An Anthropic-format adapter exists, but it is not an officially supported interface in this reference. Do not configure Claude/Anthropic-specific clients against the OpenAI endpoint based solely on the compatibility label.
Direct GPU-host features and future V3 features are separate from the live public V1 contract. There is no documented V1 reservation or guaranteed priority-lane request option.
Model-specific parameters
V1 forwards original chat request fields while using a narrower view for validation, routing, and billing. Fields such as tools, reasoning controls, and response_format still depend on the selected model and upstream service.
Use stop as an array of strings in V1. Unlike some other compatible APIs, a plain string is not accepted by its typed request parser.
The image-generation handler accepts a size field but does not forward it to its configured backend. Do not rely on it to select output dimensions.
Give these docs to a coding assistant
Start with llms.txt, which lists the individual Markdown guides and reference pages. Load only the relevant pages for a task, or use llms-full.txt when the full text is needed.
OpenAPI JSON contains the request and response schemas. Every reference page is generated from that same contract so field tables and schema downloads share a source.
Static HTML and Markdown
Every page's main content and navigation are present in the HTML response; no React application or JavaScript execution is needed to read them. Markdown versions are linked from each page and use the same content source.
Optional local JavaScript adds search, copy controls, code-language tabs, and theme selection. It does not gate documentation access behind a login or fetch the main text after page load.
Security contact
Report vulnerabilities privately to security@stageone.solutions. The security policy and security.txt describe the reporting channel and testing boundaries.