// head_to_head
Qwen3.6 Plus vs Inkling Small
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.
Inkling Small is the cheaper of the two; neither can be ranked on quality here.
Inkling Small 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.
qwen
Qwen3.6 Plus
- Blended / 1M
- $0.731
- Context
- 1M
- Released
- Apr 2, 2026
- Overall score
- 68.9
thinkingmachines
Inkling Small
- Blended / 1M
- $0.637
- Context
- 1.0M
- Released
- Jul 30, 2026
- Overall score
- Not evaluated
Specs and pricing
| Metric | Qwen3.6 Plus | Inkling Small |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | 68.9 | — |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.1262 | — |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $0.731 | $0.637win |
| Input price / 1M | $0.325win | $0.450 |
| Output price / 1M | $1.95 | $1.20win |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | — | $0.100 |
| Context window | 1M | 1.0M |
| Max output tokens | 66K | 262Kwin |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Qwen3.6 Plus on top, Inkling Small 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 | Qwen3.6 Plus | Inkling Small |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $234.00/mo | $178.80/mo |
| RAG assistant 8K in / 600 out × 100K requests | $377.00/mo | $292.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $416.00/mo | $260.00/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $471.25/mo | $522.50/mo |
| Bulk classification 500 in / 20 out × 5M requests | $1,008/mo | $1,070/mo |
Which should you pick?
You are cost-constrained
Inkling Small
Cheaper on blended list price at $0.637 per million tokens.
Qwen3.6 Plus vs Inkling Small FAQ
Which is better, Qwen3.6 Plus or Inkling Small?
Inkling Small is the cheaper of the two; neither can be ranked on quality here. Inkling Small 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 Qwen3.6 Plus cheaper than Inkling Small?
Inkling Small is cheaper. On a 3:1 input:output blend, Qwen3.6 Plus lists at $0.731 per million tokens and Inkling Small at $0.637 — Inkling Small is 15% cheaper. Input and output are priced separately — Qwen3.6 Plus charges $0.325 in and $1.95 out, Inkling Small charges $0.450 and $1.20 — so the model that looks cheaper flips depending on how output-heavy your workload is.
Does Qwen3.6 Plus or Inkling Small have a bigger context window?
They are effectively the same — 1M for Qwen3.6 Plus and 1.0M for Inkling Small.
Do Qwen3.6 Plus and Inkling Small support prompt caching?
Inkling Small publishes a cached-input rate of $0.100 per million tokens against a full input rate of $0.450. The catalogue lists no separate cached rate for Qwen3.6 Plus, which means the provider does not price it separately here — not that caching is unavailable.
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.