Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Amazon Anthropic Cohere DeepSeek Google MiniMax Mistral Moonshot AI OpenAI Qwen xAI Xiaomi MiMo Z.ai

Providers

Amazon 8 Anthropic 31 Cohere 35 DeepSeek 5 Google 34 MiniMax 17 Mistral 53 Moonshot AI 18 OpenAI 106 Qwen 26 xAI 26 Xiaomi MiMo 4 Z.ai 22
Mistral mistral-large-2407

Mistral Large 2.0 (Mistral)

Retired

Yes — Mistral Large 2.0 is retired. Mistral deprecated it on November 30, 2024 and shut it down on March 30, 2025; API requests to it now fail. The recommended replacement is Mistral Large 3.

The 123B model that made Mistral competitive with GPT-4 class systems in mid-2024, and the first Large released with downloadable weights under a research licence. It also holds the longest deprecation runway in the Mistral table: announced 30 November 2024, shut down 30 March 2025, four full months.

The facts

Provider Mistral
Model id mistral-large-2407
Released —
Deprecated November 30, 2024
Shutdown March 30, 2025 · 491 days ago
Status Retired
Last verified August 3, 2026

What to use instead

Mistral Large 3 mistral-large-3-25-12 Provider-recommended Active

What parameters mistral-large-3-25-12 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": "mistral-large-2407"
+ "model": "mistral-large-3-25-12"

Frequently asked questions

When did Mistral Large 2.0 shut down?
Mistral Large 2.0 shut down on March 30, 2025. API requests to it fail from that date onward.
What replaces Mistral Large 2.0?
Mistral recommends Mistral Large 3 (`mistral-large-3-25-12`) as the replacement for Mistral Large 2.0.
Is Mistral Large 2.0 still available?
No. Mistral Large 2.0 is retired and no longer served — it was shut down on March 30, 2025. Calls to it return an error.
How do I migrate from Mistral Large 2.0 to mistral-large-3-25-12?
Swap the model id in your API call: replace "mistral-large-2407" with "mistral-large-3-25-12". Keep the rest of the request the same, then re-check the parameters the new model accepts before you ship.

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:

[![mistral-large-2407](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/mistral/mistral-large-2407.json)](https://modeldeprecations.dev/mistral/mistral-large-2407)

Other Mistral models

All Mistral 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.