Tech
DeepSeek reroutes V4-Pro API traffic to V4.1-Flash at 04:00 UTC today, at Flash rates, until V4.1-Pro ships
DeepSeek API docs / MarkTechPost · 2026-09-14 · Source ↗
DeepSeek reroutes V4-Pro API traffic to V4.1-Flash at 04:00 UTC today, at Flash rates, until V4.1-Pro ships
DeepSeek API docs / MarkTechPost · 2026-09-14 · Source ↗
DeepSeek's API changelog note, first published alongside the V4.1-Flash launch on Wednesday, told customers that the retiring deepseek-v4-pro alias would keep accepting traffic until 04:00 UTC on Monday, at which point every subsequent request would be served by V4.1-Flash and billed at Flash rates until a V4.1-Pro variant becomes available. The cutover is soft rather than hard: existing v4-pro client configurations continue to work, but the underlying model handling the request is now V4.1-Flash, and the invoicing line item on customer bills for those requests drops to Flash pricing. DeepSeek did not publish a specific timeline for V4.1-Pro; the current Hugging Face repository contains a 51-page technical report for Flash and no Pro-tier weights.
V4.1-Flash is the fifth-generation refresh of DeepSeek's flagship line. The architecture is a 552-billion-parameter Mixture-of-Experts backbone organized as a 40-layer Causal Encoder-Decoder split evenly between a 20-layer encoder and 20-layer decoder. During prefill only 8 billion parameters are active per token; during decode 16 billion are active, roughly matching Qwen 3.5 32B decode compute at three times the effective parameter count. The FP4 KV cache combined with cross-layer attention reuse reduces the global KV footprint to approximately 890 bytes per token, a quarter of V4-Flash's footprint and the smallest published KV cache at frontier scale. Pretraining covered 45 trillion multimodal tokens at a 7:1 text-to-multimodal ratio, and the context window is one million tokens with native image and video understanding.
"From 12:00 Beijing time on September 14, 2026, requests to deepseek-v4-pro are served by V4.1 Flash and billed at Flash prices, until V4.1 Pro releases." — DeepSeek API changelog
What the price change costs the customer
V4-Pro's public price at retirement was roughly $8 per million input tokens and $24 per million output tokens on cached reads. V4.1-Flash lands at $2.10 input and $8 output. Customers whose workloads route through v4-pro today will see roughly a 66-percent price cut on input tokens and a comparable drop on output, and DeepSeek's routing preserves the model identifier so no client-side change is required. The tradeoff, and the reason the cutover is not framed as a straight discount, is that V4.1-Flash's active-parameter budget is smaller than V4-Pro's. On the harder end of DeepSeek's own internal reasoning benchmarks, Flash trails V4-Pro by two to four percentage points depending on task class. For most inference workloads the tradeoff is favorable; for workloads that were price-blind and reasoning-intensive, customers will want to wait for V4.1-Pro or route to a competing frontier model.
How the retirement folds into the pacing debate
The V4-Pro retirement is the first frontier-model retirement to happen inside the pace-the-frontier week and it is instructive as a shape. DeepSeek did not slow anything down: it accelerated. The company retired an old flagship four weeks after new-model launch and pushed customers onto the cheaper, faster new variant while a further-scaled Pro tier gets trained. That cadence, three-week major-version refresh, one-week retirement window, is the pattern Amodei's essay wants embedded evaluators to slow. DeepSeek is not a signatory to any pacing framework and remains explicitly outside the democratic-coordination step in Amodei's plan, so the retirement is also the first observable point at which the pacing coalition and the open-weights frontier diverge in real customer-facing product decisions.