// head_to_head
Kimi K2.6 vs Palmyra X5
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.
Kimi K2.6 is the cheaper of the two; neither can be ranked on quality here.
Palmyra X5 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.
moonshotai
Kimi K2.6
- Blended / 1M
- $1.71
- Context
- 262K
- Released
- Apr 20, 2026
- Overall score
- 70.5
Specs and pricing
| Metric | Kimi K2.6 | Palmyra X5 |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | 70.5 | — |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.0918 | — |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $1.71win | $1.95 |
| Input price / 1M | $0.950 | $0.600win |
| Output price / 1M | $4.00win | $6.00 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.160 | — |
| Context window | 262K | 1.0Mwin |
| Max output tokens | 236Kwin | 8K |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Kimi K2.6 on top, Palmyra X5 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 | Kimi K2.6 | Palmyra X5 |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $491.12/mo | $624.00/mo |
| RAG assistant 8K in / 600 out × 100K requests | $684.00/mo | $840.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $637.60/mo | $960.00/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $1,211/mo | $1,050/mo |
| Bulk classification 500 in / 20 out × 5M requests | $2,380/mo | $2,100/mo |
Which should you pick?
You need to fit large documents in one call
Palmyra X5
Wider context window — 1.0M against 262K.
You are cost-constrained
Kimi K2.6
Cheaper on blended list price at $1.71 per million tokens.
Kimi K2.6 vs Palmyra X5 FAQ
Which is better, Kimi K2.6 or Palmyra X5?
Kimi K2.6 is the cheaper of the two; neither can be ranked on quality here. Palmyra X5 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 Kimi K2.6 cheaper than Palmyra X5?
Kimi K2.6 is cheaper. On a 3:1 input:output blend, Kimi K2.6 lists at $1.71 per million tokens and Palmyra X5 at $1.95 — Kimi K2.6 is 14% cheaper. Input and output are priced separately — Kimi K2.6 charges $0.950 in and $4.00 out, Palmyra X5 charges $0.600 and $6.00 — so the model that looks cheaper flips depending on how output-heavy your workload is.
Does Kimi K2.6 or Palmyra X5 have a bigger context window?
Palmyra X5 has the larger context window: 262K for Kimi K2.6 against 1.0M for Palmyra X5. 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 Kimi K2.6 and Palmyra X5 support prompt caching?
Kimi K2.6 publishes a cached-input rate of $0.160 per million tokens against a full input rate of $0.950. The catalogue lists no separate cached rate for Palmyra X5, 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.