DeepSeek V4 Pro
DeepSeek V4 Pro remains listed under deepseek-v4-pro as the V4-Pro-0813 backend on the current price page. The current changelog says Pro service continues after September 14 with unchanged billing. An older September 10 announcement still says requests would redirect to V4.1 Flash, so verify backend identity and billing when that distinction matters.
The August 13 announcement resolves the earlier catalog-only boundary: V4 Pro is now explicitly GA on app, web, and API, and DeepSeek documents production gains plus flexible reasoning effort. The `0813` backend label still does not prove that a separately versioned 0813 checkpoint or architecture report exists.
Checked October 7: the current pricing table lists V4-Pro-0813 separately, and the changelog says V4 Pro service continues unchanged after user demand. The older September 10 release article still announces a Flash redirect. That remaining first-party disagreement is narrower than the earlier conflict: current pricing and changelog no longer support the redirect claim.
- Evaluate DeepSeek API pricing for long-context chat and agent workflows.
- Compare cache-hit and cache-miss token costs before running coding-agent loops.
- Use tool calls, JSON output, Responses API, and thinking mode in DeepSeek API experiments.
- Screen DeepSeek V4 Pro against GPT, Claude, Gemini, and Qwen model choices.
The current price table lists DeepSeek-V4-Pro-0813 with its own text-only contract and Pro rates, and the current changelog says service continues after September 14 with unchanged billing. The older September 10 V4.1 Flash announcement still says Pro requests will redirect until V4.1 Pro launches. Use the current catalog for documented terms, preserve the remaining announcement conflict, and inspect your actual response and bill before assuming the backend behind an ID.
DeepSeek now explicitly calls V4 Pro generally available across app, web, and API. The request model remains `deepseek-v4-pro`, the hosted backend is `DeepSeek-V4-Pro-0813`, and the release adds documented low, high, and max reasoning effort plus native Responses API support optimized for Codex.
- Stable request model ID: `deepseek-v4-pro`; current hosted backend: `DeepSeek-V4-Pro-0813`.
- API surfaces: https://api.deepseek.com and https://api.deepseek.com/anthropic.
- Current feature boundary: JSON output, tool calls, Responses API, Anthropic API, chat prefix completion beta, and FIM in non-thinking mode.
Since August 16, DeepSeek charges V4 Pro $0.022 cache-hit input, $0.66 cache-miss input, and $1.98 output per 1M tokens off peak; peak rates are $0.044, $1.32, and $3.96. Peak hours are 01:00–04:00 and 06:00–10:00 UTC, Monday through Friday, and the account concurrency limit remains 500. The old uniform $0.003625/$0.435/$0.87 rates and future-increase warning are no longer current.
The official API catalog proves the hosted backend transition, but the official Hugging Face repository still exposes the generic `deepseek-ai/DeepSeek-V4-Pro` checkpoint and its model card still calls the V4 series a preview. DeepSeek has not published a separately identified 0813 checkpoint, architecture delta, launch benchmark table, or detailed 0813 changelog, so those claims remain unverified.
Hacker News and Reddit are useful here for demand and wording: users are asking whether DeepSeek has created a new low-cost floor for long-context agent work. Those discussions should not override DeepSeek pricing docs, and users should recheck the official pricing page before committing spend.
The API-selection fields that make DeepSeek V4 Pro comparable with other model endpoints.
Long-running harnesses are where cache behavior, tool calling, and output cost become operational decisions.
DeepSeek V4 Pro is not local, but it is often evaluated as a low-cost hosted escalation or provider-native option.
The company behind the V4 model family, DeepSeek Chat, public APIs, and open-weight research releases.
The July 31 API release adds re-post-training, native Responses API support, and an official Codex integration path.
Separate experimental API model for mixed text and image input; V4 Pro remains text-only.
DeepSeek-native coding agent that makes cache-aware API behavior visible in a terminal workflow.
High-end Anthropic coding and agent model used in cost and quality comparisons.
OpenAI frontier model used as a long-context and coding-agent comparison point.
Google Flash-tier model positioned around agentic coding, multimodal input, and long-horizon workflows.
Source confidence
DeepSeek API Docs
DeepSeek API Docs
DeepSeek API Docs
DeepSeek API Docs
DeepSeek API Docs
DeepSeek / Hugging Face
NIST CAISI
Reddit / r/vibecodingitalia
DeepSeek V4 Pro FAQ
Common questions about DeepSeek V4 Pro.
Does deepseek-v4-pro now route to V4.1 Flash?+
The current price page and changelog document continued V4 Pro service with separate Pro pricing. The older September 10 announcement still says it would route to V4.1 Flash; the remaining conflict does not justify claiming that all current official pages announce a redirect. Check the returned backend and billing if you need a pinned deployment.
What does DeepSeek V4 Pro cost now?+
DeepSeek now uses peak and off-peak pricing. Off peak, V4 Pro costs $0.022 cache-hit input, $0.66 cache-miss input, and $1.98 output per 1M tokens; peak rates are $0.044, $1.32, and $3.96. Peak hours are 01:00–04:00 and 06:00–10:00 UTC, Monday through Friday.
Is DeepSeek V4 Pro officially released?+
Yes. DeepSeek's August 13 announcement explicitly makes V4 Pro generally available on app, web, and API. The stable API ID remains `deepseek-v4-pro`, mapped to the `DeepSeek-V4-Pro-0813` backend.
Does DeepSeek V4 Pro support the Responses API?+
Yes. DeepSeek's current Models & Pricing table lists Responses API support for both `deepseek-v4-pro` and `deepseek-v4-flash`.
Can I download DeepSeek-V4-Pro-0813 weights?+
DeepSeek has not published a separately identified `DeepSeek-V4-Pro-0813` checkpoint. The official Hugging Face repository provides MIT-licensed `deepseek-ai/DeepSeek-V4-Pro` weights, but its model card still describes the public V4 series as a preview, so do not assume those files are the hosted 0813 backend.
Why does cache-hit pricing matter for coding agents?+
Coding agents repeatedly send project context, tool results, plans, diffs, and review instructions. If the provider cache hits, repeated input can be much cheaper; if it misses, long sessions can become expensive. That makes cache policy a practical harness decision rather than a minor billing detail.