Prove the route with one small request.
Create a key, pin a current model ID, run a bounded request, and keep the usage record with the dated rate.
Start with the question in front of you.
QuickstartRun the smallest useful request and diagnose the first error.AuthenticationCreate, store, test, revoke, and rotate an API key.Chat CompletionsUse the verified core request shape and inspect usage.StreamingHandle SSE status, chunks, termination, and disconnects.ErrorsSeparate credentials, balance, permissions, throttling, and upstream failure.Models and pricingDiscover model IDs, then verify the dated USD rate snapshot.OpenAPI 3.1Read the machine-readable request and pricing contract.
Public request contract
| Need | Endpoint | Evidence |
|---|---|---|
| List account-visible model IDs | GET /v1/models | Authenticated response |
| Send a chat request | POST /v1/chat/completions | Response + usage |
| Check dated public rates | GET /api/v1/pricing | Snapshot checked 2026-09-10 |
| Inspect service state | GET /status | Public status page |
Keep the layers separate.
The public rate snapshot is planning evidence. The request ledger is the account charge. A supplier's direct rate is neither of those.