Versioning and deprecation

The live Spot gateway is /v1. The production host is https://api.aispotmarket.com. This www host does not serve the API.

Versioning

The version is the first path segment: /v1/chat/completions, /v1/sellers/{id}/asks.
Additive, backward-compatible changes stay on the current path.
Breaking changes ship under a new path (/v2, …). /v1 keeps working until its Sunset date.
OpenAPI info.version is the document revision (today 1.0.0). It is not a second URL version.

There is no API-Version request header. Send the version in the path.

How deprecation is signaled

When an operation or a whole URL version is going away, every response for that route includes:

Header	Spec	Value
`Deprecation`	RFC 9745	`true`, or an HTTP-date of the deprecation instant
`Sunset`	RFC 8594	HTTP-date after which the route may return `410 Gone`
`Link`	RFC 8288	`<https://aispotmarket.com/docs/api/versioning/>; rel="deprecation"`

Sunset is at least 90 days after Deprecation. Until Sunset, the old route remains callable. After Sunset it may disappear without a further header change.

Current /v1 operations are not deprecated, so these headers are absent. Treat a response without Deprecation / Sunset as the supported surface.

What agents should do

Pin integrations to a path version (/v1), not to “latest”.
If Deprecation is present, migrate before Sunset.
Read OpenAPI info.description for the same policy in the spec.

See API conventions and Versions.