Skip to main content

22 changes verified October 28, 2026

Know what will break before it ships.

A source-backed compatibility database for AI APIs. Find model shutdowns, exact error symptoms, affected identifiers, and the migration fix before production finds them for you.

  • Official sources monitored by cron
  • Exact model and parameter IDs
  • Visible verification dates
Stack compatibility planLocal scan

Your input stays in this browser. Nothing is uploaded or stored.

22Verified changes
12Platforms monitored
6Upcoming cutoffs
100%Official-source records

Change ledger

Recently announced or effective

Browse all changes →
MicrosoftAzure AI Foundrymedium

codex-mini: model retirement on November 15, 2026

Microsoft documents a model retirement affecting codex-mini on November 15, 2026. No replacement identifier passed the evidence gate.

model retirementSearch repositories and deployment configuration for codex-mini. No replacement identifier passed the evidence gate. Follow the linked provider documentation for the required request or behavior change.
Together AITogether AIhigh

MiniMaxAI/MiniMax-M3: model retirement on November 6, 2026

Together AI documents a model retirement affecting MiniMaxAI/MiniMax-M3 on November 6, 2026. The source lists MiniMaxAI/MiniMax-M3.1-Flash as a replacement identifier.

model retirementSearch repositories and deployment configuration for MiniMaxAI/MiniMax-M3. The official source lists MiniMaxAI/MiniMax-M3.1-Flash as a replacement identifier. Test the migration against current provider documentation before production.
xAIxAI APIlow

grok-imagine-image-quality: model retirement on November 2, 2026

xAI documents a model retirement affecting grok-imagine-image-quality on November 2, 2026. The source lists grok-imagine-image-2.0 as a replacement identifier.

model retirementSearch repositories and deployment configuration for grok-imagine-image-quality. The official source lists grok-imagine-image-2.0 as a replacement identifier. Test the migration against current provider documentation before production.
MistralMistral APImedium

zai-glm-5-2: model retirement on October 31, 2026

Mistral documents a model retirement affecting zai-glm-5-2 on October 31, 2026. The source lists zai-glm-5-3 as a replacement identifier.

model retirementSearch repositories and deployment configuration for zai-glm-5-2. The official source lists zai-glm-5-3 as a replacement identifier. Test the migration against current provider documentation before production.
xAIxAI APIhigh

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.

model retirementSearch repositories and deployment configuration for grok-voice-transcribe-1.0. The official source lists grok-voice-transcribe-2.0 as a replacement identifier. Test the migration against current provider documentation before production.
MistralMistral APImedium

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.

model retirementSearch repositories and deployment configuration for labs-leanstral-1-5. No replacement identifier passed the evidence gate. Follow the linked provider documentation for the required request or behavior change.

From symptom to fix

A changelog that answers the next question.

Provider announcements tell you what changed. Each record here also maps the affected surface, the observable failure, and the practical migration step.

  1. 1Paste a model ID, parameter, code fragment, or error.
  2. 2Match it against source-backed provider announcements.
  3. 3Open the source receipt and apply the migration fix.
anthropic / request.pyHTTP 400 → valid request
response = client.messages.create(
    model="claude-opus-4-8",
-   temperature=0.2,
-   top_p=0.9,
+   system="Be concise and factual.",
    messages=messages,
)

Evidence over volume

Every claim should be inspectable.

See what qualifies for the registry, how dates are handled, and what “verified” means.

Read the methodology →