Official cutoffs · 12 monitored platforms
AI model shutdown and API deprecation deadlines
A date-ordered calendar of breaking AI platform changes. Every deadline links to the exact affected identifiers, observable symptoms, replacement, and official provider source.
Verified October 26, 2026
Upcoming deadlines
Ordered by the platform's announced shutdown or effective date. Verify again before making a production cutover.
grok-imagine-image-quality: model retirement on November 2, 2026
The official source lists grok-imagine-image-2.0 as a replacement identifier. Test the migration against current provider documentation before production.
xAI · xAI API11 days leftMiniMaxAI/MiniMax-M3: model retirement on November 6, 2026
The official source lists MiniMaxAI/MiniMax-M3.1-Flash as a replacement identifier. Test the migration against current provider documentation before production.
Together AI · Together AI20 days leftcodex-mini: model retirement on November 15, 2026
No replacement identifier passed the evidence gate. Follow the linked provider documentation for the required request or behavior change.
Microsoft · Azure AI Foundry31 days leftVertex AI Extensions: api sunset on November 26, 2026
The official source lists Agent Platform as a replacement identifier. Test the migration against current provider documentation before production.
Google · Vertex AI44 days leftgpt-4o: model retirement on December 9, 2026
The official source lists gpt-5.6-sol as a replacement identifier. Test the migration against current provider documentation before production.
Microsoft · Azure AI FoundryBreaking behavior
Already in effect
These changes can affect current requests now, even when a provider has not announced a future shutdown date.
claude-opus-4-1-20250805: model retirement on August 5, 2026
Anthropic documents a model retirement affecting claude-opus-4-1-20250805 on August 5, 2026. The source lists claude-opus-4-8 as a replacement identifier.
Claude Opus 4.7 and later reject non-default sampling parameters
Anthropic has deprecated temperature, top_p, and top_k on Claude Opus 4.7 and later; non-default values return an HTTP 400 error.
Claude Sonnet 5 changes thinking defaults and token counts
Claude Sonnet 5 enables adaptive thinking by default, removes manual thinking budgets, rejects non-default sampling parameters, and tokenizes the same text into roughly 30% more tokens.
Gemini deprecates temperature, top_p, and top_k
Gemini 3.6 Flash and 3.5 Flash-Lite ignore the sampling parameters; Google says future model generations will return HTTP 400 when they are supplied.
gpt-5-chat: model retirement on May 13, 2026
Microsoft documents a model retirement affecting gpt-5-chat on May 13, 2026. The source lists gpt-chat-latest as a replacement identifier.
gpt-5-chat: model retirement on June 29, 2026
Microsoft documents a model retirement affecting gpt-5-chat on June 29, 2026. The source lists gpt-chat-latest as a replacement identifier.
/v1/experimental/generate_prompt, /v1/experimental/improve_prompt, and 1 more: api sunset on August 17, 2026
Anthropic documents a api sunset affecting /v1/experimental/generate_prompt, /v1/experimental/improve_prompt, and 1 more on August 17, 2026. No replacement identifier passed the evidence gate.
TimeGEN-1: model retirement on August 31, 2026
Microsoft documents a model retirement affecting TimeGEN-1 on August 31, 2026. The source lists TimeGPT-1 and TimegGPT-2.1 as replacement identifiers.
labs-leanstral-1-5: model retirement on September 30, 2026
Mistral documents a model retirement affecting labs-leanstral-1-5 on September 30, 2026. No replacement identifier passed the evidence gate.
grok-voice-transcribe-1.0: model retirement on October 2, 2026
xAI documents a model retirement affecting grok-voice-transcribe-1.0 on October 2, 2026. The source lists grok-voice-transcribe-2.0 as a replacement identifier.
How to use this deadline calendar
Search your repositories and deployment configuration for every affected model ID, endpoint, SDK symbol, and request parameter. Migrate in staging before the listed date, then regression-test response shape, tool use, token consumption, latency, and cost.
Dates are recorded as calendar dates exactly as providers publish them. When a provider does not state a stable time and timezone, plan to finish the migration before that date begins.