Kimi K2.6
kimi-k2.6RealtimeGlobal
- Input
- $0.95
- Cache read
- $0.16
- Output
- $4
- Context
- 262K
Calculate Kimi API costs across official model, context, cache, and batch pricing scopes.
Enter monthly workload, tokens, and quality pass rates. The calculator resolves eligible price bands, then shows cost per accepted answer and the candidate break-even pass rate.
Candidate break-even: 59.6% pass rate. Your scenario assumes 85%.
Warm cache-read scenario, not general ROI. It excludes cache writes/storage, tools, regional uplifts, retries, and quality failures. A dash means no published cache-read rate.
Kimi K3 pricing ↗Batch, cache, and standard request prices describe different execution modes. Use the card matching the actual request path rather than assuming the lowest listed rate applies.
Rates are USD per one million tokens. Future and transitional cards remain labeled with their effective dates instead of silently replacing today’s tier.
| Provider / model | Price scope | Input USD / 1M | Cache read USD / 1M | Output USD / 1M | Context | Source |
|---|---|---|---|---|---|---|
Kimi / Moonshot AIKimi K2.6kimi-k2.6 | RealtimeGlobal | $0.95 | $0.16 | $4 | 262K | Official ↗ |
Kimi / Moonshot AIKimi K2.7 Code Highspeedkimi-k2.7-code-highspeed | Realtime · high-speed tierGlobal | $1.90 | $0.38 | $8 | 262K | Official ↗ |
Kimi / Moonshot AIKimi K2.7 Codekimi-k2.7-code | RealtimeGlobal | $0.95 | $0.19 | $4 | 262K | Official ↗ |
Kimi / Moonshot AIKimi K3kimi-k3 | RealtimeGlobal | $3 | $0.3 | $15 | 1.05M | Official ↗ |
Rates in USD per 1M tokens
kimi-k2.6RealtimeGlobal
kimi-k2.7-code-highspeedRealtime · high-speed tierGlobal
kimi-k2.7-codeRealtimeGlobal
kimi-k3RealtimeGlobal
USD per 1M tokens. Snapshot verified 2026-08-16. Cache writes, cache storage, tools, regions, and provider-specific thresholds may be billed separately.
A missing cache rate is shown as “—”, never treated as free. Consumer chat-plan quotas are not API prices.
Batch, cache, and standard request prices describe different execution modes. Use the card matching the actual request path rather than assuming the lowest listed rate applies.
Count retries, fallbacks, tool calls, latency failures, and answers rejected by the quality rubric. A lower estimated token bill is useful only when the workload still succeeds.
Open the controlled A/B labThis page uses TokenGauge’s 2026-08-16 official-source snapshot. Follow the linked provider pages before making a production commitment because prices can change.
No. It models input, output, and a warm cache-read share. Cache writes or storage, tools, retries, regional uplifts, taxes, batch modes, and quality failures can change the final invoice.
No. ChatGPT, Claude, Gemini, Grok, Kimi, and other consumer-plan quotas are separate from provider API token billing.