// head_to_head

Inkling 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.

OpenRouter + LiveBenchAll comparisonsFull leaderboard

Inkling 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.

thinkingmachines

Inkling

Blended / 1M
$1.76
Context
1.0M
Released
Jul 17, 2026
Overall score
71.9
reasoningtool callingimage inputaudio inputprompt caching

writer

Palmyra X5

Blended / 1M
$1.95
Context
1.0M
Released
Jan 21, 2026
Overall score
Not evaluated

Specs and pricing

MetricInklingPalmyra X5
LiveBench overall

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

71.9
Cost per point

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

$0.1766
Blended price / 1M

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

$1.76win$1.95
Input price / 1M$1.00$0.600win
Output price / 1M$4.05win$6.00
Cached input / 1M

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

$0.170
Context window1.0M1.0M
Max output tokens472Kwin8K

Benchmarks by category

An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Inkling on top, Palmyra X5 below, both out of 100.

Agentic coding
49.4
Coding
71.0
Reasoning
78.3
Mathematics
88.4
Data analysis
72.8
Language
73.5
Instruction following
70.1

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.

WorkloadInklingPalmyra X5
Support chatbot

1.2K in / 400 out × 200K requests

$504.24/mo$624.00/mo
RAG assistant

8K in / 600 out × 100K requests

$711.00/mo$840.00/mo
Coding agent

40K in / 4K out × 20K requests

$659.20/mo$960.00/mo
Document extraction

20K in / 1.5K out × 50K requests

$1,262/mo$1,050/mo
Bulk classification

500 in / 20 out × 5M requests

$2,490/mo$2,100/mo
Run these two through the cost calculator

Which should you pick?

You are cost-constrained

Inkling

Cheaper on blended list price at $1.76 per million tokens.

Inkling vs Palmyra X5 FAQ

Which is better, Inkling or Palmyra X5?

Inkling 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 Inkling cheaper than Palmyra X5?

Inkling is cheaper. On a 3:1 input:output blend, Inkling lists at $1.76 per million tokens and Palmyra X5 at $1.95 — Inkling is 11% cheaper. Input and output are priced separately — Inkling charges $1.00 in and $4.05 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 Inkling or Palmyra X5 have a bigger context window?

They are effectively the same — 1.0M for Inkling and 1.0M for Palmyra X5.

Do Inkling and Palmyra X5 support prompt caching?

Inkling publishes a cached-input rate of $0.170 per million tokens against a full input rate of $1.00. 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.
  • 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.