DeepSeek V4 Pro Lands with 1.6T Parameters, 1M Context, and a Coding Edge
A 1M-token context window that actually runs at 27% of the compute cost of the previous generation changes the economics of long-document processing and multi-step agent workflows. Coding benchmarks that beat GPT-5.4 and Gemini 3.1 Pro on LiveCodeBench and Codeforces, at a fraction of the output price, make V4 Pro a credible default for code-generation pipelines.
DeepSeek V4 Pro uses a Mixture-of-Experts architecture with 1.6T total parameters and 49B activated, supporting a 1M-token context window and up to 384K tokens of output. A hybrid attention design combining compressed sparse and heavily compressed attention cuts single-token inference FLOPs to 27% of V3.2 and KV cache usage to 10%, making million-token contexts practical rather than theoretical. The model also adopts manifold-constrained hyper-connections for training stability at scale and the Muon optimizer for faster convergence across 32T+ pre-training tokens.
On LiveCodeBench, V4 Pro Max scores 93.5 versus Gemini 3.1 Pro's 91.7, and its Codeforces rating of 3206 edges out GPT-5.4 xHigh at 3168. Agent benchmarks put it in the same tier as Opus 4.6 and Gemini 3.1 Pro, with an 80.6% solve rate on SWE Verified. Three inference modes—Non-Think, Think High, and Think Max—let developers trade speed for depth depending on the task.
Pricing starts at 0.025 yuan per million cached input tokens and 6 yuan per million output tokens, with a concurrency cap of 500. The API supports JSON structured output, tool calls, and both OpenAI and Anthropic protocol formats, so existing integrations can switch by changing a base URL and key.
Cutting KV cache to 10% of the previous generation at full 1M context is the kind of efficiency gain that turns a spec-sheet number into a usable feature; most long-context claims still carry prohibitive latency and memory costs.
V4 Pro's coding lead over GPT-5.4 and Gemini 3.1 Pro on LiveCodeBench and Codeforces, combined with output pricing roughly an order of magnitude cheaper, pressures Western labs on the price-performance ratio for developer tools.
The two-stage post-training strategy—training domain experts separately, then distilling them into one model—sidesteps the interference that makes joint multi-task fine-tuning brittle, and it explains how a single model can stay competitive across coding, math, and agent tasks simultaneously.
Offering three explicit reasoning modes with documented response formats gives developers a predictable cost-latency-quality tradeoff, which is more operationally useful than a single opaque 'smart' mode.