Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Anthropic Cohere DeepSeek Google MiniMax Mistral Moonshot AI OpenAI xAI Z.ai

Providers

Anthropic 29 Cohere 35 DeepSeek 5 Google 24 MiniMax 17 Mistral 53 Moonshot AI 18 OpenAI 103 xAI 26 Z.ai 22

Moonshot AI deprecated models

Every Moonshot AI model we track, split by where it is in its life: what is shutting down and when, what has already gone, and what is still safe to build on. 18 models, current as of August 3, 2026.

Shutting down (7) Retired (7) Active (4)

Shutting down

Announced shutdown dates, soonest first. These still answer requests until the date lands.

Model Status Shutdown Replacement
Kimi K2.5
kimi-k2.5
 Deprecated August 31, 2026
in 28 days
 kimi-k2.6
Moonshot v1 128k
moonshot-v1-128k
 Deprecated August 31, 2026
in 28 days
 kimi-k2.6
Moonshot v1 128k Vision Preview
moonshot-v1-128k-vision-preview
 Deprecated August 31, 2026
in 28 days
 kimi-k2.6
Moonshot v1 32k
moonshot-v1-32k
 Deprecated August 31, 2026
in 28 days
 kimi-k2.6
Moonshot v1 32k Vision Preview
moonshot-v1-32k-vision-preview
 Deprecated August 31, 2026
in 28 days
 kimi-k2.6
Moonshot v1 8k
moonshot-v1-8k
 Deprecated August 31, 2026
in 28 days
 kimi-k2.6
Moonshot v1 8k Vision Preview
moonshot-v1-8k-vision-preview
 Deprecated August 31, 2026
in 28 days
 kimi-k2.6

Retired

Already removed. Requests to these models fail.

Model Status Shutdown Replacement
Kimi K2 (0711)
kimi-k2-0711-preview
 Retired May 25, 2026
70 days ago
 kimi-k2.6
Kimi K2 (0905)
kimi-k2-0905-preview
 Retired May 25, 2026
70 days ago
 kimi-k2.6
Kimi K2 Thinking
kimi-k2-thinking
 Retired May 25, 2026
70 days ago
 kimi-k2.6
Kimi K2 Thinking Turbo
kimi-k2-thinking-turbo
 Retired May 25, 2026
70 days ago
 kimi-k2.6
Kimi K2 Turbo
kimi-k2-turbo-preview
 Retired May 25, 2026
70 days ago
 kimi-k2.7-code-highspeed
Kimi Latest
kimi-latest
 Retired January 28, 2026
187 days ago
 kimi-k3
Kimi Thinking Preview
kimi-thinking-preview
 Retired November 11, 2025
265 days ago
 kimi-k2.6

Active

No deprecation and no shutdown date announced as of the last check.

Model Status Shutdown Replacement
Kimi K2.6
kimi-k2.6
 Active — —
Kimi K2.7 Code
kimi-k2.7-code
 Active — —
Kimi K2.7 Code Highspeed
kimi-k2.7-code-highspeed
 Active — —
Kimi K3
kimi-k3
 Active — —

Keep up with Moonshot AI deprecations

Shutdown dates land with months of notice and then arrive all at once. Subscribe to the calendar and they show up alongside everything else you plan around.

Subscribe (.ics) RSS Full calendar

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.