DeepSeek R1 API pricing
DeepSeek's reasoning model. Available at listed at platform rate (no published official USD price).
| Route | Input / 1M | Output / 1M |
|---|---|---|
| Platform rate | $0.2899 | $1.1596 |
USD, standard tier. Rate read from the live rate config on 2026-11-14. DeepSeek publishes no USD list price for this model, so nothing here is cross-checked against one — this is a gateway rate, not a discount.
Specifications
| Vendor | DeepSeek |
| Context window | — |
| Max output | — |
| Category | China |
What DeepSeek R1 costs at your volume
| Usage level | Input / output per month | Monthly cost |
|---|---|---|
| Light, prototyping, a few thousand calls | 5M / 1M | $2.61 |
| Working (one developer), daily use | 50M / 10M | $26.09 |
| Heavy — team or agent loops in production | 500M / 100M | $260.91 |
Calculated at $0.2899 input / $1.1596 output per 1M tokens, 4.0× apart on this model, assuming a 5:1 input-to-output ratio. That ratio is the single largest source of error in this table: resend-heavy workloads drift well past it, and at 4.0× the correction is not linear. The cost calculator takes the actual figures.
What DeepSeek R1 is for
$0.2899 per million input tokens puts DeepSeek R1 low enough that volume stops being the first question. This is a model you can point at thousands of calls a day and not think about: summarisation at scale, autocomplete, extraction pipelines, tier-one filtering in front of a stronger model.
Two honest limits. At 4.0×, output is still the majority of the bill, so this is not the cheapest option for genuinely long generation. And at this price the saving from staying cheap is small — escalating a hard case to a flagship costs pennies next to the cost of getting it wrong.
Where DeepSeek R1 sits in the index
DeepSeek R1 is 87 of 231 on input rate and 85 of 231 on output rate. A gap of 2 places, because on this model the output rate is 4.0× the input rate, level with the index median of 4.0× An output-heavy workload therefore leaves it almost where it started, which is why the cheapest model per input token is routinely not the cheapest per task. Percentile is the share of the 231 models in this index that cost more than DeepSeek R1.
| Ranked by | Position | Percentile | Rate |
|---|---|---|---|
| Input rate | 87 of 231 | 62% | $0.2899 |
| Output rate | 85 of 231 | 63% | $1.1596 |
| Agent mix 1:3, blended | 84 of 231 | 64% | $0.9422 |
On an agent mix the lowest blended rate in the same index is Gemma2 9B It at $0.01 per 1M tokens (about 94).2× less than this model at the same ratio. Across the whole index, sorting by input price alone moves a model by as much as 77 places; on DeepSeek R1 specifically the shift is 2 — which is what the re-ranked index exists to show.
DeepSeek R1 is 87 of 231 across every model in the index; the comparison that usually settles a choice is DeepSeek's own lineup further down.
DeepSeek R1 among DeepSeek's 4 models
DeepSeek R1 is the 3rd cheapest of DeepSeek's 4 models in this index at $0.2899 per 1M input tokens. The range inside that group runs from DeepSeek V4.1 Flash at $0.15 to DeepSeek V4 Pro at $0.66, a spread of 4×, and this one sits at 1.9× the group's cheapest tier.
| Model | In / 1M | Out / 1M | vs this |
|---|---|---|---|
| DeepSeek V4.1 Flash | $0.15 | $0.6 | 0.52× |
| DeepSeek V4 Flash | $0.22 | $0.66 | 0.76× |
| DeepSeek R1 | $0.2899 | $1.1596 | — |
| DeepSeek V4 Pro | $0.66 | $1.98 | 2.28× |
On input rate alone, stepping up to DeepSeek V4 Pro costs 2.3× the input rate and dropping to DeepSeek V4 Flash cuts it by 24%. Both measured at 2026-11-14, the same check as every other rate on this page.
Full DeepSeek range, including models outside this shortlist: DeepSeek rate index.
Similarly priced alternatives
| Similarly priced | Vendor | In / out per 1M | vs this |
|---|---|---|---|
| Gemini 2.5 Flash | $0.15 / $1.251 | −$0.05 | |
| GPT-5 mini | OpenAI | $0.125 / $1 | −$0.32 |
| DeepSeek V4 Flash | DeepSeek | $0.22 / $0.66 | −$0.57 |
Blended comparison (input + output per 1M). Price is one axis, these are the three closest to DeepSeek R1 in blended rate, not interchangeable substitutes for it.
Calling DeepSeek R1
The identifier you send is DeepSeek-R1. Copy it exactly, because a mismatch
returns a model error rather than a connection error, which sends most people to debug the wrong
thing. Everything else is a base URL argument, DeepSeek R1's own SDKs work unchanged.
from openai import OpenAI
client = OpenAI(base_url="https://aicomp.ai/v1", api_key="sk-...")
resp = client.chat.completions.create(
model="DeepSeek-R1",
messages=[
{"role": "system", "content": "Answer in one short paragraph."},
{"role": "user", "content": "Explain what changed in this release."},
],
max_tokens=300,
)
# prompt_tokens / completion_tokens 是真实账单的唯一依据 —— 记下来,别猜
print(resp.usage.prompt_tokens, resp.usage.completion_tokens)
Log the usage object on every call, not just while you are optimising. On DeepSeek R1 output costs 4.0× what input costs, so the same monthly token count bills very differently depending on how much of it comes back as output — measure your own split before extrapolating from the headline input rate, because rates move with vendor promotions.
Setting it up
Pointing an existing integration at DeepSeek R1 is a base URL change, not a rewrite. Pick your tool:
- Claude Code — set the base URL via environment variables
- Cursor — override the API endpoint in settings
- OpenAI / Anthropic SDK — one
base_urlargument - Python (sync), streaming and async examples
- Cutting the bill — eight levers ranked by effect
What different usage shapes cost on DeepSeek R1
A monthly token budget does not convert cleanly into a monthly invoice, and DeepSeek R1 is an ordinary case rather than an extreme one: output is priced at 4.0× input, level with the median of 4.0× across the 231 models in our index. Everything follows from that one number, at 5:1 it is manageable, at 1:1 the same token count costs half as much. Below are five shapes real DeepSeek R1 deployments fall into, each costing it out at the split it actually produces.
| Workload | Tokens | Output share | Monthly cost | vs cheapest in index |
|---|---|---|---|---|
| Classification / tagging 100k short jobs, 300 in / 20 out | 32M | 6% | $11.0162 | 9.6× |
| Support triage 20k conversations, 1.5k in / 400 out | 38M | 21% | $17.9738 | 7.6× |
| RAG question answering 50k questions, 6k in / 500 out | 325M | 8% | $115.96 | 9.3× |
| Agent loop (coding) 8k sessions, 400k in / 6k out | 3248M | 1% | $983.3408 | 11.0× |
| Long-form generation 5k documents, 2k in / 4k out | 30M | 67% | $26.091 | 6.1× |
The cheapest comparison is GPT-5 nano at $0.025 / $0.2 per 1M — 6.4× cheaper than DeepSeek R1 on a blended rate. Treat it as a rate floor, not a recommendation: it says nothing about whether GPT-5 nano can do the work you need DeepSeek R1 for.
Read the table as a sanity check rather than a forecast. If your own output share sits anywhere near 3%, everything above is priced almost entirely at DeepSeek R1's $0.2899 input rate; at 40% the $1.1596 output rate has taken the larger half. Nobody's split is exactly the one you assumed when you picked the model, which is why the calculator asks for it before quoting anything.
FAQ
How much does DeepSeek R1 cost per million tokens?
$0.2899 per million input tokens and $1.1596 per million output tokens. No official USD list price is published for this model, so it is billed at platform rate.
Is DeepSeek R1 cheaper than buying direct?
There is no published official USD price to compare against for this model It is billed at platform rate, and the reason to route it through a gateway is access and consolidated billing rather than a discount.
What does DeepSeek R1 cost per month in practice?
At a 5:1 input-to-output ratio it is about $2.61 a month for light use (5M input tokens) and roughly $260.91 for heavy use (500M input). Agent workloads sit at the high end here because every turn resends the context and DeepSeek R1 bills output at 4.0x input — see what actually drives Claude Code cost.
Which models cost about the same as DeepSeek R1?
The comparison table further up this page lists the three closest to DeepSeek R1's $1.4495 blended rate. If you are choosing on cost alone, test the top two on your own prompts — $0.2899 per input token is only half the equation, the other half is how many tokens a model needs before it finishes the task.
How do I start using DeepSeek R1?
You need an API key, then point your client at the gateway base URL with DeepSeek-R1 as the model id. On DeepSeek R1 it is a one-line change in most SDKs — see the SDK setup guide, or the Claude Code and Cursor guides for those tools. The DeepSeek R1 snippet is in the calling section above.
What is the DeepSeek R1 API price per 1M tokens?
$0.2899 per 1M input and $1.1596 per 1M output. The two directions are quoted separately because a request is billed twice, once for what you send, once for what comes back, and on DeepSeek R1 they differ by 4.0x.
How much more does DeepSeek R1 charge for output than input?
Output tokens cost 4.0x what input tokens do here — $0.2899 per 1M in against $1.1596 per 1M out. The median output-to-input multiple across our full price index is 4.0x, so this model sits below that line. It matters more than it looks: on DeepSeek R1 a coding agent's output takes 44% of the bill, so the input rate people usually compare is the smaller half. See why output pricing dominates.
How much does DeepSeek R1 cost for a coding agent?
About $260.91 a month at 500M input and 100M output tokens (the shape a coding assistant really produces), because every turn resends the whole context and the model writes more than it reads. The biggest lever is not the model but how much context you resend each turn, at 261 dollars a month on DeepSeek R1, halving the resend roughly halves that. See what actually drives agent cost.
Does DeepSeek R1 have an official list price?
No (DeepSeek does not publish a USD list price for this model), so there is nothing to compare against and it bills at platform rate: $0.2899 in / $1.1596 out per 1M. The reason to route it through a gateway is access and one consolidated bill across vendors, not a discount.