// head_to_head
Kimi K2.7 Code vs SpaceXAI: Grok Build 0.1
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.7 Code and SpaceXAI: Grok Build 0.1 are close on both score and price.
Neither model separates itself on published score or list price. Pick on the things this table cannot measure: latency under your load, context window headroom, tool-calling reliability, and whichever provider you already have a contract with.
moonshotai
Kimi K2.7 Code
- Blended / 1M
- $1.35
- Context
- 262K
- Released
- Jun 12, 2026
- Overall score
- 68.4
x-ai
SpaceXAI: Grok Build 0.1
- Blended / 1M
- $1.25
- Context
- 256K
- Released
- May 20, 2026
- Overall score
- 67.8
Specs and pricing
| Metric | Kimi K2.7 Code | SpaceXAI: Grok Build 0.1 |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | 68.4 | 67.8 |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.0545 | $0.0144win |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $1.35 | $1.25 |
| Input price / 1M | $0.670win | $1.00 |
| Output price / 1M | $3.40 | $2.00win |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.170win | $0.200 |
| Context window | 262K | 256K |
| Max output tokens | 262K | — |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Kimi K2.7 Code on top, SpaceXAI: Grok Build 0.1 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.7 Code | SpaceXAI: Grok Build 0.1 |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $396.80/mo | $342.40/mo |
| RAG assistant 8K in / 600 out × 100K requests | $540.00/mo | $600.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $528.00/mo | $512.00/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $900.00/mo | $1110.00/mo |
| Bulk classification 500 in / 20 out × 5M requests | $1765.00/mo | $2300.00/mo |
Which should you pick?
You are running this at volume
SpaceXAI: Grok Build 0.1
Lowest measured cost per point of capability at $0.0144 per point — the gap compounds with every request.
Kimi K2.7 Code vs SpaceXAI: Grok Build 0.1 FAQ
Which is better, Kimi K2.7 Code or SpaceXAI: Grok Build 0.1?
Kimi K2.7 Code and SpaceXAI: Grok Build 0.1 are close on both score and price. Neither model separates itself on published score or list price. Pick on the things this table cannot measure: latency under your load, context window headroom, tool-calling reliability, and whichever provider you already have a contract with.
Is Kimi K2.7 Code cheaper than SpaceXAI: Grok Build 0.1?
They cost about the same. Both land near $1.35 per million tokens on a 3:1 input:output blend, so price is unlikely to be the deciding factor between them.
Kimi K2.7 Code vs SpaceXAI: Grok Build 0.1: which scores higher on benchmarks?
Kimi K2.7 Code scores 68.4 and SpaceXAI: Grok Build 0.1 scores 67.8 overall on LiveBench, the mean of its seven categories. That gap is inside the range that effort settings alone move a score, so treat them as equivalent on published quality. 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, Kimi K2.7 Code or SpaceXAI: Grok Build 0.1?
SpaceXAI: Grok Build 0.1. 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. Kimi K2.7 Code works out at $0.0545 per point and SpaceXAI: Grok Build 0.1 at $0.0144.
Does Kimi K2.7 Code or SpaceXAI: Grok Build 0.1 have a bigger context window?
They are effectively the same — 262K for Kimi K2.7 Code and 256K for SpaceXAI: Grok Build 0.1.
Do Kimi K2.7 Code and SpaceXAI: Grok Build 0.1 support prompt caching?
Both publish a cached-input rate: $0.170 per million for Kimi K2.7 Code and $0.200 for SpaceXAI: Grok Build 0.1, against full input rates of $0.670 and $1.00. 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-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.