deepseek-v4-pro-0813
DeepSeek/Open weights/4 providers
DeepSeek-V4-Pro-0813 is the official release of DeepSeek-V4-Pro, superseding the preview version, with greatly enhanced agentic capabilities and performance improvements that are especially pronounced in production environments. It is built on the DeepSeek-V4-Pro (Preview) model structure, with a DSpark speculative decoding module attached.MoreLess
Which id to call
deepseek-v4-proRequesty routes this id across every provider serving deepseek-v4-pro-0813, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.
From /1M input
$1.30
DeepInfra Inc.
Context
1.0M
1.0M output
Best first token
531ms
TensorX Ltd.
Price spread
1.3x
4 endpoints
Capabilities 4/8
107/s↑ 54/s
Week of Sep 28, latest, median of 4 providers
Median tokens per second once generation starts, measured on traffic routed through Requesty through Oct 2. Hover a week to read it.moreless
The bold line starts in the week of Aug 10, the first week this model was called through Requesty, and the weeks shaded before it hold no sample for it. Each provider line is that provider's own median across every model it serves, which is the grain published per provider, so a provider line can cover weeks this model was not called in yet. The exact per-provider figures for this model are ranked below.
4 endpoints / 2 regions
Providers serving deepseek-v4-pro-0813
Provider prices, per 1M tokens. Pay as you go adds 5%, or 0% on your own keys.moreless
The two panes rank deepseek-v4-pro-0813 as measured on Requesty traffic: by the provider that served it, and by the region the request came from, where the share is how much of that region's traffic this model carries. Whole-window figures, because that is the grain Requesty publishes per provider and per region.
By provider
Median tokens per second once generation starts. Bar length is the value, so the longest bar wins.moreless
Whole-window figures as published, not an average of weekly points.
By traffic region
Median tokens per second once generation starts. Bar length is the value, so the longest bar wins.moreless
Whole-window figures as published, not an average of weekly points.
| Rank | Cost 10wk | Privacy | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 |  DeepInfra Inc. | Global | 1.0M | $1.30 | $2.60 | $0.10 | 694ms | 96.0 | 97.9% | zdr | |
| 2 | DeepSeek | Global | 1M | $1.32 | $3.96 | $0.04 | 1.11s | 38.0 | 99.6% | no-train | |
| 3 |  Fireworks AI | Global | 1M | $1.32 | $3.96 | $0.04 | 1.51s | 63.0 | - | zdr | |
| 4 |  TensorX Ltd. | EU | 1.0M | $1.75 | $3.50 | $0.44 | 531ms | 224.0 | 99.0% | zdr |
A column is blank where no qualifying sample exists, and every row links to that provider's endpoint page.
model=
Which id to call
One base url, https://router.requesty.ai/v1, and one key for every id here.
deepseek-v4-proRequesty routes this id across every provider serving deepseek-v4-pro-0813, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.
OpenAI compatible
Call it in three lines
Change the base url, use your Requesty key, set the model to any id on the left. Existing OpenAI SDK code needs no other edit.
123456789101112131415from openai import OpenAI client = OpenAI( api_key="YOUR_REQUESTY_API_KEY", base_url="https://router.requesty.ai/v1", ) response = client.chat.completions.create( model="deepseek-v4-pro", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ], ) print(response.choices[0].message.content)
Artificial Analysis
Benchmark scores
Artificial Analysis Coding Index: a composite of coding evaluations including LiveCodeBench, SciCode and Terminal-Bench.
Graduate-level physics, chemistry & biology questions designed to resist Googling.
Artificial Analysis Intelligence Index: a composite of multiple evaluations measuring overall model capability.
Scores from artificialanalysis.ai. They measure the model, not the provider, so they are the same on every endpoint above.
6
More from DeepSeek
deepseek-v4.1-flash
1.0M ctx/from $0.15/9 providers
deepseek-v4-flash-vision-exp
1.0M ctx/from $0.22/1 provider
deepseek-v4-flash-0731
1.0M ctx/from $0.07/9 providers
deepseek-v4-pro-0424
1.0M ctx/from $1.04/4 providers
deepseek-v4-flash-0424
1.0M ctx/from $0.07/4 providers
deepseek-v4-pro
1.0M ctx/from $1.75/1 provider
Reference
deepseek-v4-pro-0813 questions
Which providers serve deepseek-v4-pro-0813?
deepseek-v4-pro-0813 is available from 4 providers through Requesty: DeepInfra Inc., DeepSeek, Fireworks AI, TensorX Ltd.. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does deepseek-v4-pro-0813 cost?
Pricing starts at $1.30 per million input tokens and $2.60 per million output tokens on DeepInfra Inc., the cheapest endpoint. Prices vary by provider and region; the table above shows every endpoint. Those are the upstream provider rates: pay as you go adds 5% on top, or 0% if you bring your own provider keys.
Is deepseek-v4-pro-0813 open weights?
Yes. deepseek-v4-pro-0813 is an open-weights model from DeepSeek, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.
What is the context window of deepseek-v4-pro-0813?
deepseek-v4-pro-0813 supports up to 1.0M tokens of context, with up to 1.0M output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
Which provider is fastest for deepseek-v4-pro-0813?
In recent production traffic through Requesty, TensorX Ltd. had the lowest median time to first token (531ms) for deepseek-v4-pro-0813. Latency shifts over time, so Requesty's latency-based routing picks the fastest healthy provider per request automatically.
How do I use deepseek-v4-pro-0813 with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "deepseek-v4-pro" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call deepseek-v4-pro-0813 by its managed id or a provider id?
Use the managed id, "deepseek-v4-pro". Requesty picks which of the 4 providers serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. There is also an EU-only id, "deepseek-v4-pro@eu", which routes the same way but only through EU-hosted providers. Send a provider id like "deepinfra/deepseek-v4-pro-0813" only when you need one specific deployment and want no failover.
Route deepseek-v4-pro-0813 through one endpoint
One key for 4 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in.