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
Moonshot AI kimi-latest

Kimi Latest (Moonshot AI)

Retired

Yes — Kimi Latest is retired. Moonshot AI shut it down on January 28, 2026; API requests to it now fail. The recommended replacement is Kimi K3.

A floating alias that always resolved to whatever model the Kimi consumer app was running, with automatic context caching attached. Moonshot discontinued it on 28 January 2026, which is the unusual part: most providers keep a latest pointer forever precisely so they never have to retire one.

The facts

Provider Moonshot AI
Model id kimi-latest
Released —
Deprecated date not published
Shutdown January 28, 2026 · 187 days ago
Status Retired
Last verified August 3, 2026

What to use instead

Moonshot AI Kimi K3 kimi-k3 Provider-recommended Active

There is no floating id in the current range. You now have to name a specific model, which means picking up new releases is a deliberate change rather than something that happens to you overnight.

What parameters kimi-k3 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": "kimi-latest"
+ "model": "kimi-k3"

Frequently asked questions

When did Moonshot AI Kimi Latest shut down?
Moonshot AI Kimi Latest shut down on January 28, 2026. API requests to it fail from that date onward.
What replaces Moonshot AI Kimi Latest?
Moonshot AI recommends Kimi K3 (`kimi-k3`) as the replacement for Moonshot AI Kimi Latest. There is no floating id in the current range. You now have to name a specific model, which means picking up new releases is a deliberate change rather than something that happens to you overnight.
Is Moonshot AI Kimi Latest still available?
No. Moonshot AI Kimi Latest is retired and no longer served — it was shut down on January 28, 2026. Calls to it return an error.
How do I migrate from Moonshot AI Kimi Latest to kimi-k3?
Swap the model id in your API call: replace "kimi-latest" with "kimi-k3". There is no floating id in the current range. You now have to name a specific model, which means picking up new releases is a deliberate change rather than something that happens to you overnight.

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:

[![kimi-latest](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/moonshot/kimi-latest.json)](https://modeldeprecations.dev/moonshot/kimi-latest)

Other Moonshot AI models

All Moonshot AI 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.