Versioning

The version is part of the address, immediately after the first segment; each prefix is versioned independently — there is no site-wide version number.

The version segment in the address

https://api.deepraxis.com/{protocol}/{version}/…

Under vendor prefixes, version-related headers (such as Anthropic's anthropic-version) are passed through to the vendor as-is, behaving exactly like the official API.

What counts as breaking

Removing fields, changing a field's type or meaning, changing defaults, tightening validation, changing what an error code means. Adding fields, adding endpoints, and loosening validation are not breaking.

Beta and GA

• Beta: marked "Beta" on the endpoint page. May change at any time with no compatibility promise; fine for trying out, not recommended for production.
• GA: breaking changes ship only as a new version segment (e.g. /model/v2/…); the old version keeps working.

How deprecation is announced

When an old version or endpoint is deprecated:

1. A changelog announcement, with a replacement path;
2. That endpoint's responses carry two standard headers: Deprecation (RFC 9745, when it was deprecated) and Sunset (RFC 8594, when it goes away), plus a Link header pointing to migration notes;
3. At least 90 days between announcement and shutdown; afterwards it returns 404.

Deprecation: @1767225600
Sunset: Sat, 04 Apr 2026 00:00:00 GMT
Link: </docs/changelog>; rel="deprecation"