Starting at 12:00 noon Beijing time today (04:00 UTC), every API request hitting the deepseek-v4-pro endpoint is no longer served by the 1.6-trillion-parameter flagship — it is served by the 552B V4.1-Flash, billed at Flash rates. DeepSeek's official announcement from September 10 puts it bluntly: "We're phasing out V4-Pro." A flagship that went generally available barely a month ago has just been succeeded by the smallest model in the company's lineup.
A leadership change without a launch event
Start with the timeline. V4.1-Flash arrived on September 10 as the smallest member of a new architecture family, with native visual understanding. The same announcement previewed the retirement plan: from 04:00 UTC on September 14, all deepseek-v4-pro requests route to V4.1-Flash at V4.1-Flash rates, and this stays in effect until V4.1-Pro launches. The older V4-Flash and V4-Flash-Vision-Exp are retired too, with the old model names temporarily routing for compatibility. No launch event, no rebranding — one announcement plus one routing change, and the flagship changed hands.
The model being replaced is not old stock. Per Unite.AI's report, V4-Pro only graduated from a near-four-month preview on August 12: 1.6T total parameters, 49B active per token, and more than 1.4 million downloads on Hugging Face in the last month. From general availability to retirement: 33 days.
Why 552B can take over from 1.6T
The answer is in the architecture. V4.1-Flash uses a new Causal Encoder–Decoder design: just 8B active parameters on the input side per token, 16B on the output side — a small model reads the prompt, a bigger one writes the answer, and both ends save compute. Its KV cache needs only 1/4 the HBM and 1/8 the SSD storage of the previous generation, and DeepSeek notes that cache-hit charges often account for a large share of agent costs — shrink the cache, shrink the bill.
On performance, the official wording is that "tests by multiple parties put V4.1-Flash ahead of V4-Pro on performance, cost, speed & total runtime." Against the pricing page captured by Unite.AI: V4-Pro lists $0.435 per million input tokens and $0.87 per million output tokens, with a concurrency cap of 500 on the Pro endpoint versus 2,500 for Flash — the flagship is actually the weaker option on throughput. The API model name is simply deepseek-flash, and official partners WorkBuddy (including CodeBuddy) and OpenCode already support it fully.
Parameter count no longer defines a flagship
The real story here is not that DeepSeek swapped a model — it's that it willingly pushed its largest model off the throne. In the MoE era, total parameters decoupled from real compute long ago: between a 1.6T model with 49B active and a 552B model with 8B/16B active, whichever serves cheaper and sustains higher effective throughput is the de facto flagship. With one routing change, DeepSeek conceded exactly that.
The signal for developers is practical: in long-context and agentic workloads, cache costs are catching up with the model's intelligence premium, and peak/off-peak pricing (off-peak at 50%) turns "when to run the job" into an engineering question. Weights and the technical report are already on Hugging Face, and the announcement ends with an invitation — "planning a large-scale deployment with 2,000 GPUs + a storage cluster? Let's talk" — so the local, private-deployment path is alive and well.
So here's the takeaway: when a lab famous for efficiency voluntarily retires its own largest model, the definition of "flagship" has already moved from the parameter table to performance per unit cost. The next time someone argues model quality by total parameter count, hand them this routing change.