benchrPricing breakdown
| Tier | K2.7-Code | K2.7-Code-Highspeed |
|---|---|---|
| Input (cache miss) | $0.95 | $1.90 |
| Input (cache hit) | $0.19 | $0.38 |
| Output | $4.00 | $8.00 |
| Throughput | standard | ~180 tok/s |
| Context window | 262,144 | 262,144 |
All five numbers per million tokens, read off platform.kimi.ai on June 23, 2026. The Highspeed column is exactly double the base model on every billed line — Moonshot prices the speed tier as a flat 2× rather than a separate rate card.
Same sticker rate as K2.6 — the difference is thinking tokens
Put the two Kimis side by side and the rate card barely moves. Kimi K2.6 bills $0.95/$4.00 with a $0.16 cache hit; K2.7-Code bills $0.95/$4.00 with a $0.19 cache hit. The cache hit is a hair more expensive here, which matters if your pipeline reuses a large system prompt thousands of times a day. Everything else on the sticker is identical.
Moonshot positions K2.7-Code around efficiency rather than a lower rate. It reports roughly 30% fewer thinking tokens on coding work than K2.6, while the listed per-token price stays the same.
Treat the reduction as a provider claim until it appears in your own usage. Log input, visible output, and billed reasoning tokens on the same representative tickets before and after migration, then compare total cost per accepted result.
When the Highspeed tier earns its 2×
K2.7-Code-Highspeed serves the same model at about 180 tokens per second, and up to roughly 260 in short-context runs, for twice the listed rate. Output is $8/1M instead of $4/1M.
Measure whether the latency reduction changes developer wait time enough to justify that premium. Asynchronous jobs, overnight evaluations, CI pipelines, and bulk refactors are usually better candidates for the standard tier.
Cost scenarios
For a coding-agent workload at 20M input + 8M output tokens per month, standard K2.7-Code costs $19 + $32 = $51/month. With a 90% input-cache hit assumption, the estimate falls to about $5.50 + $32 = $37.50/month. The same token volume on Highspeed costs $38 + $64 = $102/month.
If Moonshot's claim of roughly 30% fewer thinking tokens holds for this workload, output falls to 5.6M tokens and the standard-route estimate becomes about $19 + $22.40 = $41.40/month before caching. Measure output volume on your own tasks before applying that assumption.
Use-case fit
Consider for: coding agents and refactor pipelines; reasoning-heavy code work where lower thinking-token volume appears in the bill; and teams that want a Modified-MIT model they can evaluate for self-hosting.
Skip if: your work is general chat or writing rather than code — K2.6 covers the same price at broader strengths. Skip Highspeed entirely unless a human is waiting on the tokens.
Decision checklist
Meter the thinking-token claim before you bank on it: run a representative batch on K2.6 and K2.7-Code, log total output tokens (not just the rate), and see whether the ~30% materializes on your task mix. If it doesn't, there's no reason to switch off K2.6.
Split your traffic by latency: interactive sessions to Highspeed, everything asynchronous to the standard tier. Paying 2× across the board because a fraction of calls are interactive is the most common way to overspend on this model.