// head_to_head

DeepSeek V4 Pro 0813 vs Qwen3.8 27B

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.

OpenRouter + LiveBenchAll comparisonsFull leaderboard

DeepSeek V4 Pro 0813 scores higher, Qwen3.8 27B costs less — it depends on your workload.

DeepSeek V4 Pro 0813 is ahead by 2.2 points overall, and Qwen3.8 27B lists 1.6× cheaper per blended million tokens. Whether 2.2 points is worth that depends on how much a wrong answer costs you. The two cost measures disagree here, which is worth knowing: Qwen3.8 27B has the lower sticker price, but DeepSeek V4 Pro 0813 earns each point of capability for less — $0.0241 against $0.0556 — because per-token rates do not predict how many tokens a model actually spends on a task.

deepseek

DeepSeek V4 Pro 0813

Blended / 1M
$1.78
Context
1.0M
Released
Aug 12, 2026
Overall score
77.4
reasoningtool callingprompt caching

qwen

Qwen3.8 27B

Blended / 1M
$1.14
Context
1M
Released
Aug 14, 2026
Overall score
75.3
reasoningtool callingimage inputvideo inputprompt caching

Specs and pricing

MetricDeepSeek V4 Pro 0813Qwen3.8 27B
LiveBench overall

Mean of the seven LiveBench category scores, 0–100. Higher is better.

77.4win75.3
Cost per point

Measured benchmark spend divided by overall score — dollars per point of capability.

$0.0241win$0.0556
Blended price / 1M

3:1 input:output mix, the usual shape of production traffic.

$1.78$1.14win
Input price / 1M$1.19$0.450win
Output price / 1M$3.56$3.20win
Cached input / 1M

Price of an input token served from the prompt cache, where the provider publishes one.

$0.040win$0.050
Context window1.0M1M
Max output tokens131K

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, Qwen3.8 27B below, both out of 100.

Agentic coding
54.9
61.4
Coding
77.2
75.7
Reasoning
85.8
80.0
Mathematics
95.1
86.2
Data analysis
79.2
76.6
Language
82.1
74.3
Instruction following
67.7
72.7

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.

WorkloadDeepSeek V4 Pro 0813Qwen3.8 27B
Support chatbot

1.2K in / 400 out × 200K requests

$487.56/mo$335.20/mo
RAG assistant

8K in / 600 out × 100K requests

$704.88/mo$392.00/mo
Coding agent

40K in / 4K out × 20K requests

$592.42/mo$392.00/mo
Document extraction

20K in / 1.5K out × 50K requests

$1397.88/mo$670.00/mo
Bulk classification

500 in / 20 out × 5M requests

$2752.20/mo$1245.00/mo
Run these two through the cost calculator

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

Qwen3.8 27B

Leads on agentic coding — 61.4 against 54.9.

DeepSeek V4 Pro 0813 vs Qwen3.8 27B FAQ

Which is better, DeepSeek V4 Pro 0813 or Qwen3.8 27B?

DeepSeek V4 Pro 0813 scores higher, Qwen3.8 27B costs less — it depends on your workload. DeepSeek V4 Pro 0813 is ahead by 2.2 points overall, and Qwen3.8 27B lists 1.6× cheaper per blended million tokens. Whether 2.2 points is worth that depends on how much a wrong answer costs you. The two cost measures disagree here, which is worth knowing: Qwen3.8 27B has the lower sticker price, but DeepSeek V4 Pro 0813 earns each point of capability for less — $0.0241 against $0.0556 — because per-token rates do not predict how many tokens a model actually spends on a task.

Is DeepSeek V4 Pro 0813 cheaper than Qwen3.8 27B?

Qwen3.8 27B is cheaper. On a 3:1 input:output blend, DeepSeek V4 Pro 0813 lists at $1.78 per million tokens and Qwen3.8 27B at $1.14 — Qwen3.8 27B is 1.6× cheaper. Input and output are priced separately — DeepSeek V4 Pro 0813 charges $1.19 in and $3.56 out, Qwen3.8 27B charges $0.450 and $3.20 — so the model that looks cheaper flips depending on how output-heavy your workload is.

DeepSeek V4 Pro 0813 vs Qwen3.8 27B: which scores higher on benchmarks?

DeepSeek V4 Pro 0813 scores 77.4 and Qwen3.8 27B scores 75.3 overall on LiveBench, the mean of its seven categories. That is a 2.2-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 Qwen3.8 27B?

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 Qwen3.8 27B at $0.0556.

Does DeepSeek V4 Pro 0813 or Qwen3.8 27B have a bigger context window?

They are effectively the same — 1.0M for DeepSeek V4 Pro 0813 and 1M for Qwen3.8 27B.

Do DeepSeek V4 Pro 0813 and Qwen3.8 27B support prompt caching?

Both publish a cached-input rate: $0.040 per million for DeepSeek V4 Pro 0813 and $0.050 for Qwen3.8 27B, against full input rates of $1.19 and $0.450. 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.
  • ScoresLiveBench 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.