// head_to_head
MiniMax M3 vs Kimi K2.7 Code
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 scores higher, MiniMax M3 costs less — it depends on your workload.
Kimi K2.7 Code is ahead by 1.2 points overall, and MiniMax M3 lists 2.6× cheaper per blended million tokens. Whether 1.2 points is worth that depends on how much a wrong answer costs you. MiniMax M3 also leads on measured cost per point of capability, at $0.0339 per point.
minimax
MiniMax M3
- Blended / 1M
- $0.525
- Context
- 1.0M
- Released
- May 31, 2026
- Overall score
- 67.3
moonshotai
Kimi K2.7 Code
- Blended / 1M
- $1.35
- Context
- 262K
- Released
- Jun 12, 2026
- Overall score
- 68.4
Specs and pricing
| Metric | MiniMax M3 | Kimi K2.7 Code |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | 67.3 | 68.4win |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | $0.0339win | $0.0545 |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $0.525win | $1.35 |
| Input price / 1M | $0.300win | $0.670 |
| Output price / 1M | $1.20win | $3.40 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | $0.060win | $0.170 |
| Context window | 1.0Mwin | 262K |
| Max output tokens | 512Kwin | 262K |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — MiniMax M3 on top, Kimi K2.7 Code 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 | MiniMax M3 | Kimi K2.7 Code |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $150.72/mo | $396.80/mo |
| RAG assistant 8K in / 600 out × 100K requests | $216.00/mo | $540.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $201.60/mo | $528.00/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $378.00/mo | $900.00/mo |
| Bulk classification 500 in / 20 out × 5M requests | $750.00/mo | $1765.00/mo |
Which should you pick?
You are running this at volume
MiniMax M3
Lowest measured cost per point of capability at $0.0339 per point — the gap compounds with every request.
Quality matters more than the bill
Kimi K2.7 Code
Highest overall LiveBench score of the two at 68.4.
The workload is coding or agentic work
Kimi K2.7 Code
Leads on agentic coding — 45.7 against 40.7.
You need to fit large documents in one call
MiniMax M3
Wider context window — 1.0M against 262K.
MiniMax M3 vs Kimi K2.7 Code FAQ
Which is better, MiniMax M3 or Kimi K2.7 Code?
Kimi K2.7 Code scores higher, MiniMax M3 costs less — it depends on your workload. Kimi K2.7 Code is ahead by 1.2 points overall, and MiniMax M3 lists 2.6× cheaper per blended million tokens. Whether 1.2 points is worth that depends on how much a wrong answer costs you. MiniMax M3 also leads on measured cost per point of capability, at $0.0339 per point.
Is MiniMax M3 cheaper than Kimi K2.7 Code?
MiniMax M3 is cheaper. On a 3:1 input:output blend, MiniMax M3 lists at $0.525 per million tokens and Kimi K2.7 Code at $1.35 — MiniMax M3 is 2.6× cheaper. Input and output are priced separately — MiniMax M3 charges $0.300 in and $1.20 out, Kimi K2.7 Code charges $0.670 and $3.40 — so the model that looks cheaper flips depending on how output-heavy your workload is.
MiniMax M3 vs Kimi K2.7 Code: which scores higher on benchmarks?
MiniMax M3 scores 67.3 and Kimi K2.7 Code scores 68.4 overall on LiveBench, the mean of its seven categories. That is a 1.2-point lead for Kimi K2.7 Code. 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, MiniMax M3 or Kimi K2.7 Code?
MiniMax M3. 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. MiniMax M3 works out at $0.0339 per point and Kimi K2.7 Code at $0.0545.
Does MiniMax M3 or Kimi K2.7 Code have a bigger context window?
MiniMax M3 has the larger context window: 1.0M for MiniMax M3 against 262K for Kimi K2.7 Code. 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 MiniMax M3 and Kimi K2.7 Code support prompt caching?
Both publish a cached-input rate: $0.060 per million for MiniMax M3 and $0.170 for Kimi K2.7 Code, against full input rates of $0.300 and $0.670. 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.