// head_to_head
Nemotron 3.5 Super VL vs MiMo-V2.6-Pro
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.
MiMo-V2.6-Pro scores higher, Nemotron 3.5 Super VL costs less — it depends on your workload.
MiMo-V2.6-Pro is ahead by 18.3 points overall, and Nemotron 3.5 Super VL lists 2.3× cheaper per blended million tokens. Whether 18.3 points is worth that depends on how much a wrong answer costs you. The two cost measures disagree here, which is worth knowing: Nemotron 3.5 Super VL has the lower sticker price, but MiMo-V2.6-Pro earns each point of capability for less — $0.0018 against $0.0030 — because per-token rates do not predict how many tokens a model actually spends on a task.
nvidia
Nemotron 3.5 Super VL
- Blended / 1M
- $0.237
- Context
- 1.0M
- Released
- Oct 15, 2026
- Overall score
- 50.2
xiaomi
MiMo-V2.6-Pro
- Blended / 1M
- $0.544
- Context
- 1.1M
- Released
- Sep 21, 2026
- Overall score
- 68.5
Specs and pricing
| Metric | Nemotron 3.5 Super VL | MiMo-V2.6-Pro |
|---|---|---|
| LiveBench overall Weighted mean of the seven LiveBench category scores, 0–100. Higher is better. | 50.2 | 68.5win |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.0030 | $0.0018win |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $0.237win | $0.544 |
| Input price / 1M | $0.150win | $0.435 |
| Output price / 1M | $0.500win | $0.870 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.020 | $0.0036win |
| Context window | 1.0M | 1.1M |
| Max output tokens | 236Kwin | 131K |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Nemotron 3.5 Super VL on top, MiMo-V2.6-Pro 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 | Nemotron 3.5 Super VL | MiMo-V2.6-Pro |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $66.64/mo | $142.94/mo |
| RAG assistant 8K in / 600 out × 100K requests | $98.00/mo | $227.64/mo |
| Coding agent 40K in / 4K out × 20K requests | $87.20/mo | $176.02/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $181.00/mo | $478.68/mo |
| Bulk classification 500 in / 20 out × 5M requests | $360.00/mo | $958.80/mo |
Which should you pick?
You are running this at volume
MiMo-V2.6-Pro
Lowest measured cost per point of capability at $0.0018 per point — the gap compounds with every request.
Quality matters more than the bill
MiMo-V2.6-Pro
Highest overall LiveBench score of the two at 68.5.
The workload is coding or agentic work
MiMo-V2.6-Pro
Leads on long-horizon agentic — 35.2 against 11.7.
You are cost-constrained
Nemotron 3.5 Super VL
Cheaper on blended list price at $0.237 per million tokens.
Nemotron 3.5 Super VL vs MiMo-V2.6-Pro FAQ
Which is better, Nemotron 3.5 Super VL or MiMo-V2.6-Pro?
MiMo-V2.6-Pro scores higher, Nemotron 3.5 Super VL costs less — it depends on your workload. MiMo-V2.6-Pro is ahead by 18.3 points overall, and Nemotron 3.5 Super VL lists 2.3× cheaper per blended million tokens. Whether 18.3 points is worth that depends on how much a wrong answer costs you. The two cost measures disagree here, which is worth knowing: Nemotron 3.5 Super VL has the lower sticker price, but MiMo-V2.6-Pro earns each point of capability for less — $0.0018 against $0.0030 — because per-token rates do not predict how many tokens a model actually spends on a task.
Is Nemotron 3.5 Super VL cheaper than MiMo-V2.6-Pro?
Nemotron 3.5 Super VL is cheaper. On a 3:1 input:output blend, Nemotron 3.5 Super VL lists at $0.237 per million tokens and MiMo-V2.6-Pro at $0.544 — Nemotron 3.5 Super VL is 2.3× cheaper. Input and output are priced separately — Nemotron 3.5 Super VL charges $0.150 in and $0.500 out, MiMo-V2.6-Pro charges $0.435 and $0.870 — so the model that looks cheaper flips depending on how output-heavy your workload is.
Nemotron 3.5 Super VL vs MiMo-V2.6-Pro: which scores higher on benchmarks?
Nemotron 3.5 Super VL scores 50.2 and MiMo-V2.6-Pro scores 68.5 overall on LiveBench, the weighted mean of its seven categories. That is a 18.3-point lead for MiMo-V2.6-Pro. 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, Nemotron 3.5 Super VL or MiMo-V2.6-Pro?
MiMo-V2.6-Pro. 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. Nemotron 3.5 Super VL works out at $0.0030 per point and MiMo-V2.6-Pro at $0.0018.
Does Nemotron 3.5 Super VL or MiMo-V2.6-Pro have a bigger context window?
They are effectively the same — 1.0M for Nemotron 3.5 Super VL and 1.1M for MiMo-V2.6-Pro.
Do Nemotron 3.5 Super VL and MiMo-V2.6-Pro support prompt caching?
Both publish a cached-input rate: $0.020 per million for Nemotron 3.5 Super VL and $0.0036 for MiMo-V2.6-Pro, against full input rates of $0.150 and $0.435. 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.