Kimi pricing
Kimi API Cost Calculator
Estimate Kimi API spend for K2.7 Code, K2.6, K2.5, and Moonshot V1 using request volume, cache-hit input, cache-miss input, output tokens, budget buffer, and custom contract rates.
Kimi API cost calculator
Choose a workload, enter monthly requests and token size, then compare provider cost before committing.
- 1Pick workloadUse the closest API usage scenario.
- 2Enter tokensAdd request volume, input, output, and cache.
- 3Compare modelsCheck monthly cost and effective rate.
- 4Share or exportCopy the link or download the CSV.
Next: copy the share link or export the CSV, then request a worksheet or send a pricing correction if the assumptions need review.
| Provider | Model | Input / 1M | Cached / 1M | Output / 1M | Discount | Monthly cost | Cost / request |
|---|
Repeated context can reduce input cost
K2.7, K2.6, and K2.5 publish lower cache-hit input rates than cache-miss input rates.
Latency can change the budget
K2.7 Code HighSpeed costs more, so use it only where faster output speed matters.
Context tier matters
Moonshot V1 8K, 32K, and 128K have different input prices, so long-context routing needs its own estimate.
When Kimi API pricing analysis matters
Kimi is relevant when a team wants long-context coding, agent, multimodal, or Chinese-market model coverage without mixing CNY cloud pricing into a USD provider comparison. The main budgeting questions are cache-hit share, output length, and whether HighSpeed latency is worth the higher price.
For a low-cost USD alternative, compare with the DeepSeek API Cost Calculator. For CNY-denominated Chinese cloud prices, use the China LLM API Pricing Calculator.
| Cost lever | Why it matters for Kimi | What to check before launch |
|---|---|---|
| Cache-hit share | K2 models publish separate cache-hit and cache-miss input pricing. | Measure repeated system prompts, documents, tool context, and agent memory. |
| HighSpeed routing | The HighSpeed K2.7 Code row is more expensive than standard K2.7 Code. | Use it only for user-facing tasks where latency affects conversion or retention. |
| Context tier | Moonshot V1 input prices increase as the context window increases. | Route short prompts to smaller context rows and reserve 128K for long documents. |
FAQ
How do you estimate Kimi API cost?
Estimate monthly requests, cache-miss input tokens, cache-hit input tokens, and output tokens, then multiply each by the selected Kimi or Moonshot price per million tokens.
Which Kimi models are included?
This calculator includes Kimi K2.7 Code, Kimi K2.7 Code HighSpeed, Kimi K2.6, Kimi K2.5, and Moonshot V1 8K, 32K, and 128K pricing.
Should I compare Kimi with DeepSeek or China cloud models?
Yes. Compare Kimi with DeepSeek for USD-denominated API routing, and use the China LLM API Pricing Calculator when you need CNY-denominated Qwen, Doubao, ERNIE, or Hunyuan planning.
Sources
Kimi prices were last checked on 2026-07-05. Verify the official pricing pages before committing spend or setting customer prices.