Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Anthropic Google OpenAI

Providers

Anthropic 29 Google 24 OpenAI 103
OpenAI o1-mini

o1-mini (OpenAI)

Retired

Yes — o1-mini is retired. OpenAI deprecated it on April 28, 2025 and shut it down on October 27, 2025; API requests to it now fail. The recommended replacement is o4-mini.

The cheap reasoning model of the first o-series generation, strong on maths and code for its size but noticeably weaker on general knowledge. Retired October 2025.

The facts

Provider OpenAI
Model id o1-mini
Released September 12, 2024
Deprecated April 28, 2025
Shutdown October 27, 2025 · 276 days ago
Status Retired
Last verified July 30, 2026

What to use instead

OpenAI o4-mini o4-mini Provider-recommended Deprecated

o4-mini was the named successor and is now itself deprecated, shutting down October 2026. Two migrations in eighteen months for anyone who followed the advice each time.

What parameters o4-mini accepts on modelparams.dev

Change the id

In most cases the migration is one string. Check the parameter differences before you ship — newer models drop older sampling knobs more often than they add them. 

- "model": "o1-mini"
+ "model": "o4-mini"

Where the migration path ends

The recommended successor has itself been replaced. Following the chain to a model that is still active today:

  1. o1-mini
  2. o4-mini Deprecated
  3. gpt-5.6-terra Active

Frequently asked questions

When did OpenAI o1-mini shut down?
OpenAI o1-mini shut down on October 27, 2025. API requests to it fail from that date onward.
What replaces OpenAI o1-mini?
OpenAI recommends o4-mini (`o4-mini`) as the replacement for OpenAI o1-mini. o4-mini was the named successor and is now itself deprecated, shutting down October 2026. Two migrations in eighteen months for anyone who followed the advice each time.
Is OpenAI o1-mini still available?
No. OpenAI o1-mini is retired and no longer served — it was shut down on October 27, 2025. Calls to it return an error.
How do I migrate from OpenAI o1-mini to o4-mini?
Swap the model id in your API call: replace "o1-mini" with "o4-mini". o4-mini was the named successor and is now itself deprecated, shutting down October 2026. Two migrations in eighteen months for anyone who followed the advice each time.

Sources

Found something wrong? The data is one YAML file — edit it on GitHub.

This page, for machines

JSON Markdown Badge JSON

Drop the badge in a README so it turns red the day this model is retired:

[![o1-mini](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/o1-mini.json)](https://modeldeprecations.dev/openai/o1-mini)

Other OpenAI models

All OpenAI deprecations →

How to use this site

The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.

# How to use modeldeprecations.dev

[modeldeprecations.dev](https://modeldeprecations.dev) answers one question per model: is it deprecated,
when does it shut down, and what replaces it. Every date on the site is cited to the
provider's own documentation, with the date we last checked it.

Three lifecycle states are used, matching the providers' own vocabulary:

- **active** — still supported, no deprecation announced.
- **deprecated** — the provider has announced it is going away. It still answers requests.
- **retired** — API access is gone. Requests fail.

A model can be active *and* carry a shutdown date: Anthropic publishes a
"not sooner than" date and Google publishes an earliest shutdown date for models
that are current and fully supported. Those are reported as scheduled shutdowns,
not deprecations, because that is what the provider actually committed to.

## Check one model

```bash
curl https://modeldeprecations.dev/api/v1/models/openai/gpt-4-32k.json
```

Or fetch the page as Markdown, which includes the answer, the dates and the sources:

```bash
curl https://modeldeprecations.dev/openai/gpt-4-32k.md
```

## Full catalog

```bash
curl https://modeldeprecations.dev/api/v1/models.json
```

Ids are `provider/model`. Dated snapshots (`gpt-4-32k-0613`) are listed as aliases of
their canonical entry rather than as separate records.

Each entry carries `computed_status`, the lifecycle state recomputed against the build
date — so a model whose shutdown has passed reads `retired` without anyone editing data.

## Badges

A shields.io endpoint per model, for READMEs that should go red when a model dies:

```
https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4-32k.json
```

## Calendar and changelog

- Subscribe to every shutdown date: https://modeldeprecations.dev/calendar.ics
- Changelog RSS: https://modeldeprecations.dev/changelog.xml

## JSON Schema

```bash
curl https://modeldeprecations.dev/api/v1/schema.json
```

## Contribute

Data lives in YAML under `models/{provider}/{model}.yaml` in the
[GitHub repo](https://github.com/mnfst/modeldeprecations.dev). Every lifecycle date needs a source URL; CI rejects a
date without one. Open a PR.

## For agents

- Machine-readable overview: https://modeldeprecations.dev/llms.txt
- This guide plus every model inline: https://modeldeprecations.dev/llms-full.txt
- Any page also exists as Markdown: append `.md` to a model URL.
- In a browser, this site registers a **WebMCP** tool on `navigator.modelContext`:
  `check_model_deprecation`, `list_shutdowns`, `find_replacement`, and `get_usage_guide`.
- Parameters each model accepts are catalogued on the sibling site, https://modelparams.dev.