DeepSeek V4 Pro 0813 Is Live: Agent and Codex Changes
deepseek-v4-pro; the important changes are the new underlying version, stronger agent-oriented integration, native Responses API support, and direct Codex compatibility.DeepSeek-V4-Pro-0813 through the official API, while the callable model name remains deepseek-v4-pro. Teams do not need to invent a dated model ID or rewrite model-selection logic. They do need to rerun agent, tool-use, latency, token-consumption, and fallback evaluations because the model behind the stable alias has changed.Quick answer: what changed in DeepSeek V4 Pro 0813?
| Question | Verified answer as of August 13, 2026 |
|---|---|
| What version is served? | DeepSeek-V4-Pro-0813 |
| Did the callable model name change? | No. It remains deepseek-v4-pro |
| Does the provider support Responses API? | Yes, for deepseek-v4-flash and deepseek-v4-pro |
| Can Codex use DeepSeek directly? | Yes, through DeepSeek's documented native Responses API configuration |
| Context and maximum output | 1M-token context and up to 384K output |
| What must teams retest? | Agent completion, tool calls, streaming, token use, latency, errors, and fallbacks |
The stable alias matters more than the dated build name
There are now two identifiers with different jobs:
DeepSeek-V4-Pro-0813identifies the underlying version documented by DeepSeek.deepseek-v4-prois the callable API model name.
deepseek-v4-pro-0813 value. A dated identifier used by another provider or aggregator does not automatically become the official DeepSeek API alias.The stable alias lowers migration overhead, but it also means teams should record the evaluation date and observed behavior. If your application relies on a stable alias, a provider-side build update can change task quality, tool behavior, latency, or token usage without requiring a code change.
Why Responses API and Codex support change the agent workflow
https://api.deepseek.com as the Responses API base URL and provides shared configuration for Codex CLI, the ChatGPT desktop app, and the Codex extension for VS Code.That improves setup, but "Responses-compatible" does not mean every OpenAI Responses feature is implemented. DeepSeek explicitly documents a partial compatibility contract.
| Capability | DeepSeek Responses API status | Production implication |
|---|---|---|
| Text input, instructions, streaming | Supported | Suitable for normal text-based coding sessions |
| Function tools and server-side web search | Supported | Test tool schemas and result replay on real tasks |
apply_patch custom tool | Supported | Covers a core Codex file-editing workflow |
| Reasoning effort | Supported | Recheck quality, latency, and token cost per effort level |
| Image and file input | Not supported | Do not route multimodal repository tasks without preprocessing |
file_search, code_interpreter, computer_use, MCP tools | Ignored | Do not assume built-in tool parity from the protocol name |
previous_response_id, conversations, storage | Not supported | The API is stateless; your client must preserve required context |
| Background mode and service tier | Not supported | Long-running workflows need their own orchestration and retries |
Unsupported parameters may be silently ignored. That makes a successful HTTP response insufficient as an integration test: verify that every feature your agent depends on actually changes behavior as intended.
Current provider pricing is lower, but it is not a permanent promise
DeepSeek's pricing page currently lists the following direct-provider rates per 1M tokens:
| Model | Cache-hit input | Cache-miss input | Output |
|---|---|---|---|
deepseek-v4-flash | $0.0028 | $0.14 | $0.28 |
deepseek-v4-pro | $0.003625 | $0.435 | $0.87 |
What production teams should retest now
The 0813 update should be treated as a controlled model refresh, even though the API alias is unchanged.
| Stage | Test | Release gate |
|---|---|---|
| 1. Identity | Log model alias, evaluation date, endpoint, and route | No guessed dated ID in application code |
| 2. Offline eval | Run repository analysis, debugging, refactoring, and tool-use tasks | No material regression on critical tasks |
| 3. Protocol eval | Test streaming, function calls, web search, apply_patch, and ignored fields | Required tools complete reliably |
| 4. Cost eval | Measure input, cached input, reasoning, output, retries, and successful-task cost | Cost fits the workload budget |
| 5. Canary | Send a limited traffic share to Pro while keeping a fallback | Errors and latency stay within SLOs |
| 6. Rollout | Expand by workload, not all at once | Rollback remains available |
How EvoLink users should respond
EvoLink's role is not to turn an upstream release into a blanket migration recommendation. It is to make the model easier to compare and route alongside alternatives under one API and billing workflow.
- Check the DeepSeek V4 model page for currently exposed EvoLink endpoints, model options, and pricing.
- Evaluate
deepseek-v4-proanddeepseek-v4-flashon the same task set. - Keep a verified fallback for workloads where tool reliability or output quality matters more than list price.
- Do not assume EvoLink Responses API availability until that exact route is documented and tested.
- Monitor the DeepSeek status and fallback guide when building a production routing policy.
This approach preserves the value of a unified gateway: the model can change, but your evaluation, observability, billing, and fallback process remains consistent.
What remains unverified
The official documentation confirms the version, alias, context, output limit, current prices, Responses API compatibility, and Codex configuration. It does not yet justify universal claims that 0813 is the best coding model, that it improves every agent workload, or that it can replace a premium fallback without testing.
/v1/responses example. Those claims require an official benchmark table, a reproducible EvoLink evaluation, or a verified live route.FAQ
Is DeepSeek V4 Pro 0813 a new API model name?
DeepSeek-V4-Pro-0813 is the documented version, while the official callable model name remains deepseek-v4-pro.Do I need to change existing deepseek-v4-pro requests?
The provider model parameter does not change. You should still rerun regression tests because the build behind the stable alias has changed.
Does DeepSeek V4 Pro support the Responses API?
deepseek-v4-pro and deepseek-v4-flash as supported models.Can Codex connect without the old translation proxy?
Yes for the official DeepSeek route. DeepSeek now documents native Responses API support and a direct Codex configuration. Other gateways must document and verify their own Responses endpoint separately.
Does one setup cover Codex CLI, Desktop, and VS Code?
DeepSeek says those Codex clients share the same configuration file, so its documented setup makes the models available across the three clients.
Which tools are supported?
apply_patch custom tool are supported. Other custom tools and built-ins such as MCP, computer use, file search, and code interpreter are not supported through this compatibility layer.Are image and file inputs supported?
No. DeepSeek documents text input support; image and file inputs are not supported and image parts may be replaced with placeholder text.
Is the Responses API stateful?
previous_response_id, conversation state, storage, and background mode are not supported. The client or application must manage the required context.Where are the DeepSeek V4 Pro 0813 benchmarks?
Official-channel claims for the 0813 build cite large gains on agent-oriented suites (Terminal-Bench 2.1, DeepSWE, CyberGym), but as of August 13, 2026 DeepSeek has not published a formal benchmark table for 0813, and third-party aggregate scores still largely reflect the Preview build. Treat circulating 0813 numbers as provisional, check their sourcing, and rely on your own workload evaluation before rerouting production traffic.
Did DeepSeek V4 Pro pricing change?
The current direct-provider rates — $0.003625 per 1M cache-hit input tokens, $0.435 per 1M cache-miss input tokens, and $0.87 per 1M output tokens — remain valid until August 16, 2026 16:00 UTC, when DeepSeek's published peak/off-peak repricing takes effect (off-peak Pro: $0.022 / $0.66 / $1.98; peak is 2×). Verify the live price page before budgeting. EvoLink pricing is maintained separately on the model page.
Sources
- DeepSeek Models & Pricing
- DeepSeek Responses API guide
- DeepSeek Codex integration guide
- DeepSeek V4 Preview release
- EvoLink DeepSeek V4 model page
