Skip to main content
Stability tiers (categories that determine the change-control policy for each API endpoint) define what you can depend on in production.

​
Stable tier

Stable endpoints follow strict SemVer. You can depend on their request and response shape across minor and patch releases. Breaking changes require a major version bump.
EndpointMethodDescription
/v1/chat/completionsPOSTCreate a chat completion
/v1/modelsGETList available models

​
Preview tier

Preview endpoints carry a 6-month deprecation floor for breaking changes. Auriko announces deprecations with x-deprecation-date and x-removal-date in the OpenAPI spec.
EndpointMethodDescription
/v1/registry/providersGETList providers
/v1/registry/modelsGETList canonical models
/v1/directory/modelsGETFull model directory with pricing
/v1/workspaces/{workspace_id}/billing/balanceGETCredit balance
/v1/meGETAPI key identity

​
Reserved paths

The /v1beta/* path prefix is reserved for future use. Zero operations exist there at 1.0.

​
Change policy summary

TierBreaking changesDeprecation windowApplies to
StableMajor version bump requiredN/A (SemVer)Inference surface
PreviewAnnounced via spec extensions6 months minimumDiscovery, billing, identity
See Versioning for the full SemVer policy and deprecation process.