Deprecations

There are no active public deprecation notices.

Policy¶

Potentially breaking /v1 changes receive explicit migration or deprecation treatment. These include removing an endpoint or request field, making an optional field required, changing a field type, changing authentication, or changing established error semantics.

Adding an endpoint, optional field, model, optional capability, or safe additive response field is normally compatible. Clients should ignore response fields they do not understand and discover model capabilities dynamically.

Removed models disappear from the current model catalog. When removal requires advance notice or migration guidance, it will be listed here and in the public changelog rather than preserved as active model documentation.