Introduction
DeepSeek unveiled V4-Pro-0813 on August 13, 2026, marking the first official stable release of its flagship V4 series model. This build inherits the April preview version architecture, with core improvements driven by retraining rather than structural redesign. The model retains the 1.6T MoE parameter scale with 49B activated parameters per token. The most striking advancement is its drastically enhanced agent performance. Benchmark scores on DeepSWE, NL2Repo and DSBench-Hard have seen massive jumps. Alongside model upgrades, DeepSeek added native support for OpenAI Responses API and Anthropic API protocols, enabling seamless migration for workflows built around Claude Code and Codex. The documentation also debuted the simplified mode of DeepSeek Harness, an agent evaluation framework.
Notably, the provider issued an early warning of upcoming price increases for API services. This article systematically sorts out performance benchmarks, pricing rules, multi-protocol API access, adjustable reasoning modes, model selection guidance and frequently asked questions for engineering teams.
1. Core Upgrade Overview: Retraining-Driven Performance Gains
It is critical to clarify that V4-Pro-0813 shares the identical model architecture and parameter scale with the preview version launched in April. All capability improvements stem from revised training data and optimization strategies for agent scenarios, rather than hardware-level structural changes.
Key Static Specifications
- Total parameters: 1.6T (MoE architecture); activated parameters per token: 49B
- Context window: 1M tokens; maximum output length: 384K tokens
- Reasoning tiers: Three selectable modes — Non-Think (low latency), Think High (complex branching), Think Max (deep exhaustive reasoning)
- Architecture: Hybrid CSA (Compressed Sparse Attention) + HCA (Highly Compressed Attention). Compared to the V3 architecture, FLOPs are reduced by roughly 27%, and KV Cache memory demand drops by approximately 30%.
The model backbone remains unchanged. The targeted optimization of post-training datasets and strategies for agent tasks directly caused the nearly 300% score surge on the DeepSWE benchmark.
2. Agent Benchmark Results: From Mediocre to Industry-Leading
DeepSeek published direct comparison data between the April preview version and the new official 0813 build to quantify agent capability improvements.
| Benchmark Dataset | April Preview Version | Official 0813 Version | Growth Rate |
|---|---|---|---|
| DeepSWE (Software Engineering Agent) | 12.8 | 62.7 | +390% |
| NL2Repo (Natural Language to Code Repository) | 38.5 | 61.5 | +60% |
| DSBench-Hard (Full-stack Programming) | 33 | 67.2 | ~100% |
A score of 12.8 on DeepSWE indicates the preview model could barely complete multi-step code modification tasks. The official version’s 62.7 score enters the competitive range of mainstream agent models. As a reference point, DeepSeek V4-Flash (official July 31 release) scored 54.4 on DeepSWE, meaning V4-Pro outperforms V4-Flash by around 8 percentage points.
Third-Party Benchmark Data (V4 Pro High Mode)
External testing from BenchLM further validates the model’s comprehensive ability across domains:
| Category | Benchmark | Score |
|---|---|---|
| Code Generation | SWE-bench Verified | 79.4% |
| Code Generation | LiveCodeBench COT | 89.8% |
| Code Generation | Codeforces Rating | 2919 |
| Reasoning | GPQA Diamond | 89.1% |
| Long Context | MRCR 1M-token | 83.3% |
| Agent | Browse Feb Comp | 80.4% |
| Mathematics | HMMT Feb 2026 | 94.0% |
| Mathematics | IMOAnswerBench | 88.0% |
3. Pricing Structure: Triple the Cost of V4-Flash, Official Warning of Future Hikes
V4-Pro maintains the pricing scheme used for the preview version. The table below contrasts rates against V4-Flash official release:
| Billing Type | V4-Flash | V4-Pro | Price Multiple |
|---|---|---|---|
| Input (cache miss) | ¥1 / Million tokens | ¥3 / Million tokens | 3× |
| Input (cache hit) | ¥0.008 / Million tokens | ¥0.025 / Million tokens | ~3× |
| Output | ¥2 / Million tokens | ¥6 / Million tokens | 3× |
| Concurrency Limit | 2500 | 500 | 1/5 |
On the same day the new model launched, DeepSeek officially stated: “We plan to raise the overall pricing for DeepSeek API services in the near future, with a significant increase expected.” Teams with large-scale V4-Pro consumption plans may consider locking in usage volume under the current pricing window.
4. API Access Updates: Dual Protocol Support for Responses API and Anthropic Specification
The most important engineering update for developers is expanded protocol compatibility. V4-Pro now supports three mainstream access methods:
4.1 OpenAI Responses API (Newly Added)
4.2 Anthropic API Protocol (Newly Added)
4.3 Standard OpenAI Chat Completions (Unchanged)
Existing OpenAI-style calls require zero modification. Setting the model field to deepseek-v4-pro automatically routes traffic to the latest official version.
This multi-protocol compatibility delivers a key advantage: teams running existing Claude Code or Codex workflows can switch to V4-Pro simply by updating the base URL and API key, with almost no code adjustments.
5. Adjustable Reasoning Tiers Controlled via reasoning_effort
V4-Pro provides three reasoning modes controlled by the reasoning_effort parameter, allowing engineers to dynamically balance latency, token consumption and task complexity in production environments.
| Tier | API Parameter Value | Applicable Scenarios | Relative Token Consumption |
|---|---|---|---|
| Non-Think | none | Quick Q&A, code completion, format conversion | Lowest |
| Think High | high | Medium-complexity architecture design, competition math, long-chain agent tasks | Medium |
| Think Max | max | Deep logical reasoning, complex multi-step agent workflows | Highest |
For enterprise deployments, dynamic routing based on task type is recommended. Simple tasks using none can reduce cost and latency by more than 50%.
6. V4-Pro vs V4-Flash: Model Selection Guidance
Both models remain available online, with clear positioning differences.
| Dimension | V4-Flash (284B MoE) | V4-Pro (1.6T MoE) | |
|---|---|---|---|
| Activated Parameters | ~13B | 49B | |
| Output Price per Million Tokens | ¥2 | ¥6 | |
| Concurrency Limit | 2500 | 500 | |
| DeepSWE Score | 54.4 | 62.7 | |
| NL2Repo Score | 54.2 | 61.5 | |
| Best Fit Scenarios | High concurrency, low latency, cost-sensitive workloads | Complex reasoning, multi-step agent execution, end-to-end code generation |
Selection Recommendations
- Code generation & autonomous agent tasks: Choose V4-Pro, which holds an 8–10 percentage point advantage on agent benchmarks.
- High-concurrency RAG, real-time chat, batch processing: Choose V4-Flash to cut costs to roughly one-third of V4-Pro.
- Uncertain workloads: Run parallel testing with both models to compare output quality and latency before finalizing the model route.
7. Supporting Ecosystem: DeepSeek Harness Simplified Mode Released
DeepSeek officially introduced DeepSeek Harness simplified mode alongside the V4-Pro launch. The official documentation confirms that all published agent benchmark results (DeepSWE 62.7, NL2Repo 61.5) were generated under this simplified Harness configuration. The complete Harness framework includes advanced context management, built-in tool invocation and automated test loop capabilities. It is expected to further lift model performance in real-world agent scenarios once fully launched.
8. Frequently Asked Technical Questions
Q1: Version Compatibility of V4-Pro-0813
The identifier 0813 is a build label, transparent to the API layer. Developers continue to use deepseek-v4-pro as the model ID. Requests will automatically route to the latest official build without requiring code changes.
Q2: Timetable for the announced price increase
DeepSeek has not published a specific date, only noting the hike will arrive in the near future. Teams should monitor official API documentation for real-time updates.
Q3: Concurrency limit of 500 — Can it support large-scale enterprise workloads?
The native 500 concurrent limit may become a bottleneck for high-throughput scenarios such as massive code scanning and data analysis. Enterprises facing concurrency pressure can distribute traffic via multi-model aggregation platforms such as 4sapi. This setup enables load balancing across multiple model endpoints and automatic failover to alternate models to mitigate service interruptions.
Q4: Protocol compatibility gaps between Anthropic specification and native Claude
While V4-Pro supports the Anthropic API schema, its internal thinking mechanism differs from Claude’s extended thinking implementation. The streaming format of reasoning_content has subtle deviations. Teams migrating Claude workflows should validate critical prompt outputs before full rollout.
Q5: How to interpret the DeepSWE benchmark position
DeepSWE is DeepSeek’s internal agent benchmark. The public SWE-bench Verified universal benchmark shows V4-Pro reaches 79.4%, placing it within the tier of top open models, though still below proprietary alternatives such as Claude Opus 5 (96%).
9. Conclusion
V4-Pro-0813 represents a targeted upgrade focused on agent capability. Without modifying the underlying model architecture, retraining pushed DeepSWE scores from 12.8 to 62.7, transforming the model from nearly incapable of complex coding tasks to a competitive agent model. The dual-protocol API support (OpenAI Responses API + Anthropic) lowers migration barriers significantly. Existing teams relying on Claude Code or Codex stacks can trial V4-Pro with minimal engineering overhead. The three-tier adjustable reasoning mode offers flexible cost-performance tuning for production systems.
The V4 series now forms a complete dual-product lineup: V4-Flash serves high-concurrency, low-latency scenarios, while V4-Pro handles complex reasoning and multi-step agent workloads. The upcoming DeepSeek Harness framework will provide standardized tooling for agent evaluation. Given the official warning of upcoming price increases, engineering teams should evaluate consumption forecasting and model routing strategies in advance.
All data in this article is current as of August 13, 2026. For definitive parameters, refer to DeepSeek’s official API documentation.




