Contract pages
- Stability tiers — Stable vs Preview endpoint classification
- Versioning — SemVer policy and deprecation process
- Supported parameters — Request fields accepted by
POST /v1/chat/completions - Error codes — All error codes with HTTP statuses
- Response metadata — Fields in the
routing_metadataobject - Response headers — Custom headers returned with every response
- Canonical models — All model IDs available at launch
What the contract covers
The contract defines the shape of requests and responses for all public endpoints. You can depend on these behaviors across minor and patch releases. Fields and headers classified as HIDDEN insdk-exposure.yaml are stripped at the API boundary. They aren’t part of the public contract and don’t appear in any page above.