AI Model Lifecycle & Deprecation Index preview
Is this AI model still live? When does it sunset, and what should you migrate to? A cross-vendor record — OpenAI, Anthropic, Google, Amazon Bedrock — of model status, release/deprecation/shutdown dates, and migration targets. Every date is traceable to the provider's own official announcement.
Every row links to the provider's official deprecation/lifecycle page. Dates are transcribed from that page; fields a provider doesn't publish are left blank rather than guessed. Built for agents that need to know, at runtime, whether the model they're about to call still exists. Spotted an error or a missing model? Send a correction →
| Model | Provider | Shuts down | Migrate to |
|---|---|---|---|
| anthropic.claude-3-haiku (Bedrock) | Amazon Bedrock | 2026-09-10 | — |
| amazon.nova-premier | Amazon Bedrock | 2026-09-14 | — |
| gpt-3.5-turbo-instruct | OpenAI | 2026-09-28 | gpt-5.6-terra |
| anthropic.claude-sonnet-4 (Bedrock) | Amazon Bedrock | 2026-10-14 | — |
| gpt-4o-2024-05-13, gpt-4-turbo, o1, o4-mini | OpenAI | 2026-10-23 | gpt-5.6-sol / terra |
| gpt-5, o3 | OpenAI | 2026-12-11 | gpt-5.6-sol |
What this answers
Three questions agents and teams ask constantly, with a cited answer: is model X still callable? when is it retired? what does the provider say to migrate to? Providers now ship aggressive deprecation calendars that break production systems when a model is pulled. This index is the machine-readable, cross-vendor source of truth for that — so an agent can check a model's status before depending on it, and a team can see everything sunsetting in the next quarter in one place.
How each row is established
Each model's status and dates are transcribed from the provider's official deprecation or lifecycle page (OpenAI's deprecations page, Anthropic's model-deprecations table, Google's Gemini API deprecations, AWS's Bedrock model-lifecycle page). The exact source URL is stored on every row. Where a provider does not publish a field — for example OpenAI does not publish model release dates — it is left blank rather than inferred. Note that a model's lifecycle on a hosting platform (e.g. Amazon Bedrock) can differ from its lifecycle on the model-maker's own API; each row records which surface it describes. Days-until-shutdown is computed at request time.
How an AI agent can use it
| Access | Endpoint | Cost |
|---|---|---|
| Lifecycle of one model | GET lifecycle.oscar-lopez.com/v1/lifecycle/model?id=ID | free |
| Upcoming shutdowns (N days) | GET lifecycle.oscar-lopez.com/v1/lifecycle/deprecations?within_days=90 | free |
| All models for a provider | GET lifecycle.oscar-lopez.com/v1/lifecycle/provider?provider=openai | free |
| Full export (all models) | GET lifecycle.oscar-lopez.com/v1/lifecycle/all | free (preview) → x402 |
| MCP tools | /mcp → model_lifecycle, is_model_live, upcoming_deprecations (free); full export (preview-free) | free |
Frequently asked
How current is it?
Each row shows the date it was last verified against the provider's page. The v0 seed was verified on 8 Sep 2026; an automated re-checker is on the roadmap.
Why do some dates say "no sooner than"?
Some providers publish only a tentative earliest-retirement date for active models rather than a firm shutdown date. Those are recorded as notes, and the firm shutdown_on is left blank until the provider commits to one.
Found something wrong or missing?
Send the model id, the correct dates, and the official source URL to [email protected]. Corrections are dated and published.
Who stands behind it?
Oscar E. López, Ph.D. (Information Systems, UMass Amherst). Independent project, not affiliated with any listed provider. Not legal or engineering advice — confirm against the linked source before relying on it.