// head_to_head
Mercury 2 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.
Mercury 2 and Qwen3.8 27B are priced within ~10% of each other.
Mercury 2 does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
inception
Mercury 2
- Blended / 1M
- $0.375
- Context
- 128K
- Released
- Mar 4, 2026
- Overall score
- Not evaluated
qwen
Qwen3.8 27B
- Blended / 1M
- $0.342
- Context
- 1M
- Released
- Aug 14, 2026
- Overall score
- 58.4
Specs and pricing
| Metric | Mercury 2 | Qwen3.8 27B |
|---|---|---|
| LiveBench overall Weighted mean of the seven LiveBench category scores, 0–100. Higher is better. | — | 58.4 |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | — | $0.0084 |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $0.375 | $0.342 |
| Input price / 1M | $0.250 | $0.039win |
| Output price / 1M | $0.750win | $1.25 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.025 | $0.0039win |
| Context window | 128K | 1Mwin |
| Max output tokens | 50K | 66Kwin |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Mercury 2 on top, Qwen3.8 27B 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 | Mercury 2 | Qwen3.8 27B |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $103.80/mo | $106.83/mo |
| RAG assistant 8K in / 600 out × 100K requests | $155.00/mo | $92.16/mo |
| Coding agent 40K in / 4K out × 20K requests | $134.00/mo | $111.54/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $295.00/mo | $131.00/mo |
| Bulk classification 500 in / 20 out × 5M requests | $587.50/mo | $204.95/mo |
Which should you pick?
You need to fit large documents in one call
Qwen3.8 27B
Wider context window — 1M against 128K.
Mercury 2 vs Qwen3.8 27B FAQ
Which is better, Mercury 2 or Qwen3.8 27B?
Mercury 2 and Qwen3.8 27B are priced within ~10% of each other. Mercury 2 does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
Is Mercury 2 cheaper than Qwen3.8 27B?
They cost about the same. Both land near $0.375 per million tokens on a 3:1 input:output blend, so price is unlikely to be the deciding factor between them.
Does Mercury 2 or Qwen3.8 27B have a bigger context window?
Qwen3.8 27B has the larger context window: 128K for Mercury 2 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 Mercury 2 and Qwen3.8 27B support prompt caching?
Both publish a cached-input rate: $0.025 per million for Mercury 2 and $0.0039 for Qwen3.8 27B, against full input rates of $0.250 and $0.039. 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-10-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.