// head_to_head

Claude Opus 4.5 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

Qwen3.8 27B wins outright — it scores higher and costs less.

Qwen3.8 27B leads by 2.7 points overall while listing 8.8× 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. Qwen3.8 27B also leads on measured cost per point of capability, at $0.0556 per point.

anthropic

Claude Opus 4.5

Blended / 1M
$10.00
Context
200K
Released
Nov 24, 2025
Overall score
72.6
reasoningtool callingfile inputimage inputprompt 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

MetricClaude Opus 4.5Qwen3.8 27B
LiveBench overall

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

72.675.3win
Cost per point

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

$0.3211$0.0556win
Blended price / 1M

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

$10.00$1.14win
Input price / 1M$5.00$0.450win
Output price / 1M$25.00$3.20win
Cached input / 1M

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

$0.500$0.050win
Context window200K1Mwin
Max output tokens64K131Kwin

Benchmarks by category

An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Claude Opus 4.5 on top, Qwen3.8 27B below, both out of 100.

Agentic coding
39.7
61.4
Coding
79.7
75.7
Reasoningtoo close to call
80.1
80.0
Mathematics
90.4
86.2
Data analysis
74.4
76.6
Language
81.3
74.3
Instruction following
62.5
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.

WorkloadClaude Opus 4.5Qwen3.8 27B
Support chatbot

1.2K in / 400 out × 200K requests

$2876.00/mo$335.20/mo
RAG assistant

8K in / 600 out × 100K requests

$3700.00/mo$392.00/mo
Coding agent

40K in / 4K out × 20K requests

$3480.00/mo$392.00/mo
Document extraction

20K in / 1.5K out × 50K requests

$6650.00/mo$670.00/mo
Bulk classification

500 in / 20 out × 5M requests

$12,750/mo$1245.00/mo
Run these two through the cost calculator

Which should you pick?

You are running this at volume

Qwen3.8 27B

Lowest measured cost per point of capability at $0.0556 per point — the gap compounds with every request.

Quality matters more than the bill

Qwen3.8 27B

Highest overall LiveBench score of the two at 75.3.

The workload is coding or agentic work

Qwen3.8 27B

Leads on agentic coding — 61.4 against 39.7.

You need to fit large documents in one call

Qwen3.8 27B

Wider context window — 1M against 200K.

Claude Opus 4.5 vs Qwen3.8 27B FAQ

Which is better, Claude Opus 4.5 or Qwen3.8 27B?

Qwen3.8 27B wins outright — it scores higher and costs less. Qwen3.8 27B leads by 2.7 points overall while listing 8.8× 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. Qwen3.8 27B also leads on measured cost per point of capability, at $0.0556 per point.

Is Claude Opus 4.5 cheaper than Qwen3.8 27B?

Qwen3.8 27B is cheaper. On a 3:1 input:output blend, Claude Opus 4.5 lists at $10.00 per million tokens and Qwen3.8 27B at $1.14 — Qwen3.8 27B is 8.8× cheaper. Input and output are priced separately — Claude Opus 4.5 charges $5.00 in and $25.00 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.

Claude Opus 4.5 vs Qwen3.8 27B: which scores higher on benchmarks?

Claude Opus 4.5 scores 72.6 and Qwen3.8 27B scores 75.3 overall on LiveBench, the mean of its seven categories. That is a 2.7-point lead for Qwen3.8 27B. 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, Claude Opus 4.5 or Qwen3.8 27B?

Qwen3.8 27B. 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. Claude Opus 4.5 works out at $0.3211 per point and Qwen3.8 27B at $0.0556.

Does Claude Opus 4.5 or Qwen3.8 27B have a bigger context window?

Qwen3.8 27B has the larger context window: 200K for Claude Opus 4.5 against 1M for Qwen3.8 27B. 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 Claude Opus 4.5 and Qwen3.8 27B support prompt caching?

Both publish a cached-input rate: $0.500 per million for Claude Opus 4.5 and $0.050 for Qwen3.8 27B, against full input rates of $5.00 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.