Versioning
Stable Safe4AI sandbox REST operations use a major version in the URL path, beginning with /api/v1. Backward-compatible fields may be added within v1. Breaking request or response changes require a new major path such as /api/v2.
Deprecation and Sunset
Before removing a stable version or operation, Safe4AI publishes migration guidance and signals deprecation with RFC 9745 Deprecation and Link headers. A dated RFC 8594 Sunset header is announced at least 90 days before removal.
Compatibility alias
The unversioned /api/sandbox route remains available as a deprecated compatibility alias for /api/v1/sandbox. It returns Deprecation: true and a Sunset date. New integrations must use /api/v1/sandbox.
Rate limits
Sandbox responses include IETF RateLimit-Policy / RateLimit fields plus compatibility X-RateLimit-* headers. HTTP 429 responses include Retry-After. See rate-limit documentation.