Deprecation policy
What stays stable in the Azta API and MCP server, and how much notice breaking changes get.
Everything under /v1 of the Azta API is stable.
Changes that ship without notice
Additive changes ship without notice: new endpoints, optional request fields, response fields, enum values and error codes. Clients must ignore unknown fields and fall back on the HTTP status for error codes they do not know.
Breaking changes
Removing or renaming a field or endpoint, changing a type or a default, making a field required, changing the error code of an existing condition and changing authentication are breaking changes. Each one is announced in the changelog and its Atom feed at least 90 days before it takes effect, and the old behaviour keeps working until then.
Exceptions
An exception may take effect sooner. It is announced the same day and named in the changelog entry:
security: a security fix.legal: a change the law or a regulator requires.pre-launch: a change made before the API's public launch.
MCP server
The endpoint https://mcp.azta.ai/mcp and the tool names never change.