DEV Community

Zephyre
Zephyre

Posted on

DeepSeek retired its legacy model IDs. Is your API relay still mapping them correctly?

#ai #opensource #programming #api

DeepSeek retired the legacy deepseek-chat and deepseek-reasoner model IDs on July 24, 2026.

If you call the official endpoint directly, the migration path is relatively visible. If you use an OpenAI-compatible client or an API relay, however, a successful HTTP response does not tell you what happened to the old ID.

There are at least three possible outcomes:

  1. the relay keeps a compatibility alias and maps the old ID to a new model;
  2. the relay returns a clear migration error;
  3. the client or relay silently falls back to another route.

The third case is not automatically malicious, but it changes how you should interpret quality, price, and incidents.

My minimum check is:

  1. send one fixed, low-risk request with no production data;
  2. record the model ID sent by the client;
  3. save the response model field and the exact error class;
  4. compare the provider migration notice with the relay's model page;
  5. verify whether 400, 404, or 429 responses trigger a silent retry to another model.

For example, AllRouter's public model list still displays deepseek-reasoner. That display ID may be a compatibility alias. The name alone is not evidence that the relay is serving the retired official model, so the useful question is whether the mapping and failure behavior can be reproduced.

We are collecting sanitized results from different clients and routes in a small Telegram group: whether the old ID remains compatible, fails clearly, or is silently remapped, plus the migration steps used.

Join: https://t.me/+13g2ma9APiU0YjRl

Reply with migration + client name after joining, and we will add the relevant checklist for Claude Code, Codex CLI, the OpenAI SDK, or another client.

Disclosure: this is an AllRouter-related community, not an independent benchmark organization. No purchase is required to participate. Never share API keys, private repositories, full billing screenshots, or sensitive logs.

References:

Top comments (0)