Model deprecations
When a model is scheduled for retirement, every response from it carries Deprecation and Sunset headers (and x-ultragpt-model-replacement), the catalog marks it deprecated, and accounts that used it in the last 30 days get an email, an in-app notice and a model.deprecated webhook — at once and again a week before. After the sunset date, requests to it are answered by its replacement (header x-ultragpt-model-redirected-from) or fail with 410 model_retired. Watch the status page.
Code
curl -si https://api.ultragpt.pro/v1/chat/completions \
-H "Authorization: Bearer $ULTRAGPT_API_KEY" -H "Content-Type: application/json" \
-d '{ "model": "grok-4.7", "messages": [{ "role": "user", "content": "Hi" }] }' | grep -i -E "^(deprecation|sunset|link|x-ultragpt-model)"
# deprecation: @1790000000
# sunset: Thu, 15 Oct 2026 00:00:00 GMT
# x-ultragpt-model-replacement: newer-model
# After the sunset: answered by the replacement (x-ultragpt-model-redirected-from),
# or HTTP 410 { "error": { "code": "model_retired" } } when there is none.