// head_to_head
DeepSeek V4 Pro 0813 vs GPT-5.2-Codex
Published LiveBench scores across all seven categories, live list pricing, context windows, and the measured cost of a point of capability — for both models, side by side.
DeepSeek V4 Pro 0813 wins outright — it scores higher and costs less.
DeepSeek V4 Pro 0813 leads by 3.5 points overall while listing 2.7× cheaper per blended million tokens. There is no trade-off to reason about here; the only reason to pick the other is a constraint this table does not show, like an existing contract, a region, or a provider you are already on. DeepSeek V4 Pro 0813 also leads on measured cost per point of capability, at $0.0241 per point.
deepseek
DeepSeek V4 Pro 0813
- Blended / 1M
- $1.78
- Context
- 1.0M
- Released
- Aug 12, 2026
- Overall score
- 77.4
openai
GPT-5.2-Codex
- Blended / 1M
- $4.81
- Context
- 400K
- Released
- Jan 14, 2026
- Overall score
- 74.0
Specs and pricing
| Metric | DeepSeek V4 Pro 0813 | GPT-5.2-Codex |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | 77.4win | 74.0 |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.0241win | $0.1001 |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $1.78win | $4.81 |
| Input price / 1M | $1.19win | $1.75 |
| Output price / 1M | $3.56win | $14.00 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.040win | $0.175 |
| Context window | 1.0Mwin | 400K |
| Max output tokens | — | 128K |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — DeepSeek V4 Pro 0813 on top, GPT-5.2-Codex below, both out of 100.
What each one costs to run
Per-token prices are hard to feel. These are monthly list costs for both models across five workload shapes, using each provider's published cached-input rate where there is one.
| Workload | DeepSeek V4 Pro 0813 | GPT-5.2-Codex |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $487.56/mo | $1426.60/mo |
| RAG assistant 8K in / 600 out × 100K requests | $704.88/mo | $1610.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $592.42/mo | $1638.00/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $1397.88/mo | $2721.25/mo |
| Bulk classification 500 in / 20 out × 5M requests | $2752.20/mo | $4987.50/mo |
Which should you pick?
You are running this at volume
DeepSeek V4 Pro 0813
Lowest measured cost per point of capability at $0.0241 per point — the gap compounds with every request.
Quality matters more than the bill
DeepSeek V4 Pro 0813
Highest overall LiveBench score of the two at 77.4.
The workload is coding or agentic work
DeepSeek V4 Pro 0813
Leads on agentic coding — 54.9 against 49.4.
You need to fit large documents in one call
DeepSeek V4 Pro 0813
Wider context window — 1.0M against 400K.
DeepSeek V4 Pro 0813 vs GPT-5.2-Codex FAQ
Which is better, DeepSeek V4 Pro 0813 or GPT-5.2-Codex?
DeepSeek V4 Pro 0813 wins outright — it scores higher and costs less. DeepSeek V4 Pro 0813 leads by 3.5 points overall while listing 2.7× cheaper per blended million tokens. There is no trade-off to reason about here; the only reason to pick the other is a constraint this table does not show, like an existing contract, a region, or a provider you are already on. DeepSeek V4 Pro 0813 also leads on measured cost per point of capability, at $0.0241 per point.
Is DeepSeek V4 Pro 0813 cheaper than GPT-5.2-Codex?
DeepSeek V4 Pro 0813 is cheaper. On a 3:1 input:output blend, DeepSeek V4 Pro 0813 lists at $1.78 per million tokens and GPT-5.2-Codex at $4.81 — DeepSeek V4 Pro 0813 is 2.7× cheaper. Input and output are priced separately — DeepSeek V4 Pro 0813 charges $1.19 in and $3.56 out, GPT-5.2-Codex charges $1.75 and $14.00 — so the model that looks cheaper flips depending on how output-heavy your workload is.
DeepSeek V4 Pro 0813 vs GPT-5.2-Codex: which scores higher on benchmarks?
DeepSeek V4 Pro 0813 scores 77.4 and GPT-5.2-Codex scores 74.0 overall on LiveBench, the mean of its seven categories. That is a 3.5-point lead for DeepSeek V4 Pro 0813. Category scores differ from the overall figure — a model can lead on reasoning and trail on coding, which the per-category table above breaks out.
Which gives better value for money, DeepSeek V4 Pro 0813 or GPT-5.2-Codex?
DeepSeek V4 Pro 0813. Cost per point divides the measured dollars LiveBench spent running the benchmark by the score it earned, so it captures something token pricing misses: a reasoning model can emit many times more tokens than its per-token rate suggests. DeepSeek V4 Pro 0813 works out at $0.0241 per point and GPT-5.2-Codex at $0.1001.
Does DeepSeek V4 Pro 0813 or GPT-5.2-Codex have a bigger context window?
DeepSeek V4 Pro 0813 has the larger context window: 1.0M for DeepSeek V4 Pro 0813 against 400K for GPT-5.2-Codex. Note that a window you can fill is not a window you should fill — retrieval quality usually degrades well before the limit, and you pay for every token you put in it.
Do DeepSeek V4 Pro 0813 and GPT-5.2-Codex support prompt caching?
Both publish a cached-input rate: $0.040 per million for DeepSeek V4 Pro 0813 and $0.175 for GPT-5.2-Codex, against full input rates of $1.19 and $1.75. On a workload with a long stable prefix — a system prompt, a tool schema, a retrieved corpus — that changes the economics more than the headline price does.
Related comparisons
How these numbers are produced
- Price — provider list price from OpenRouter, refreshed every 15 minutes. “Blended” is a 3:1 input:output mix.
- Scores — LiveBench release 2026-06-25, using their own category map. Each model shows its strongest published run. A blank means “not evaluated”, never “bad”.
- Cost per point — the measured dollars LiveBench spent on the run, divided by the score it earned.
- “Win” — awarded only past a threshold: one full point on a benchmark score, 10% on a price, 25% on a context window. Anything tighter reports as a tie, because effort settings alone move a LiveBench score by more than that.
Published benchmarks rank models on someone else's tasks. Before committing, see LLM & agent evaluation for building an eval on your own.