API versioning and contract changes

The public inference base path is /v1. The checked-in OpenAPI document records the inspected contract; a versioned path is not a promise that every future change is backward compatible.

Contract source

The OpenAPI specification describes documented methods, request fields and response envelopes. Backend source snapshots and mocked tests verify code-level parity; they do not establish the exact deployed revision.

Change review

Review request and response schema changes, defaults, auth, streaming and error handling whenever you change gateway or SDK versions. Keep pinned dependencies and regression fixtures. Read the changelog.

Deprecation limits

No universal deprecation notice window or model release guarantee is established by this repository. Unknown model deprecation status remains unknown in the registry. Do not invent dates or treat a billing entry as an upstream release announcement.

Verification and next steps

These instructions describe inspected repository contracts and safe integration boundaries. They do not prove live account access or external provider behavior. Continue with developer answers, API overview and verification limits.