Skip to content
CostPerPrompt

Kimi K2.6 API Pricing

Moonshot (Kimi) · context window 262K · prices updated 2026-09-29

Input per 1M tokens
$0.65
Output per 1M tokens
$3.41
Cached input per 1M
$0.15
77% cheaper than fresh input

Where Kimi K2.6 sits on price

At $3.41 per million output tokens, Kimi K2.6 is a mid tier model — 1.6× the median output price of $2.20, which puts it cheaper than 42% and pricier than 58% of the models we track. It sits 6th cheapest of the 8 Moonshot (Kimi) models we track. Output costs 5.2× input, the usual spread — trim both, starting with the answer length.

Output tokens per $1
293,255
One full context fill
$0.1704
Cheaper than
42% of tracked models

Cached input is 77% cheaper. On an input-heavy workload you need roughly a 32% cache-hit rate to take 25% off the input line — reachable for chatbots and agents that resend the same system prompt and history.

What real workloads cost on Kimi K2.6

These three workloads are the ones teams actually run on a mid-priced model — a $3.41/1M model is not bought for the same job as one ten times the price.

Workload Per request Per month
Support chatbot — 500 conversations/day (5K in / 1.4K out) Conversation history re-sent each turn — the classic prompt-caching win. $0.008 $120
Document pipeline — 10K docs/day (3K in / 500 out) Batch-friendly: no user waiting, so a ~50% batch discount usually applies. $0.0037 $1097
Small app — 1K requests/day (500 in / 150 out) The baseline most side projects actually run at. $0.0008 $25.09

Model your exact traffic in the API cost calculator — it preloads Kimi K2.6 with caching and batch options.

Kimi K2.6 price history

Moonshot (Kimi) last cut Kimi K2.6's output price on Sep 28, 2026 (-15% per output token), from $0.95/$4.00 to $0.65/$3.41 per 1M in/out. That is one of 13 repricings in the 58 days we have tracked it — worth knowing before you hard-code today's rate into a budget.

Date Input /1M Output /1M Output change
Aug 2, 2026 (tracking began) $0.6 $3.41 —
Aug 4, 2026 $0.589 $2.48 -27%
Aug 6, 2026 $0.57 $2.40 -3%
Aug 7, 2026 $0.589 $2.48 +3%
Aug 8, 2026 $0.5795 $2.44 -2%
Aug 10, 2026 $0.95 $4.00 +64%
Aug 14, 2026 $0.5605 $2.36 -41%
Aug 15, 2026 $0.65 $3.41 +44%
Aug 16, 2026 $0.5415 $2.28 -33%
Aug 17, 2026 $0.95 $4.00 +75%
Aug 21, 2026 $0.5795 $2.44 -39%
Aug 22, 2026 $0.5415 $2.28 -7%
Aug 23, 2026 $0.95 $4.00 +75%
Sep 28, 2026 $0.65 $3.41 -15%

Change-points from our daily price snapshots (tracking since Aug 2, 2026; intraday moves between snapshots are not captured).

Kimi K2.6 vs Qwen3.5 397B A17B

The closest-priced alternative from another vendor is Qwen3.5 397B A17B (Alibaba (Qwen)) — 3% more expensive on output, with $0.1 less per million input tokens. When two models land this close on price, the decision is quality on your own workload, not the price sheet: run 50 real requests through both and compare.

See Qwen3.5 397B A17B pricing →

Cheaper alternatives

More Moonshot (Kimi) models

Frequently asked questions

› How much does the Kimi K2.6 API cost?

Kimi K2.6 costs $0.65 per million input tokens and $3.41 per million output tokens, with cached input at $0.15 per million (77% cheaper). That works out to roughly 293,255 output tokens per dollar.

› What does the support chatbot workload cost on Kimi K2.6?

Support chatbot — 500 conversations/day (5K in / 1.4K out) costs about $0.008 per request and $120 per month on Kimi K2.6. Conversation history re-sent each turn — the classic prompt-caching win.

› What does it cost to fill Kimi K2.6's 262K context window?

Sending 262K of input in a single request costs $0.1704 at $0.65 per million tokens — before any output. With prompt caching that same fill drops to about $0.0393 on repeat requests. This is why large context windows are cheap to advertise and expensive to actually use.

› Is Kimi K2.6 worth the price?

Kimi K2.6 sits in the middle of the market (6 of 8 by price within Moonshot (Kimi)). The honest test is a routing experiment: send the same 200 real requests to this model and to a tier below, and compare failure rate against the price gap — most teams find a majority of traffic never needed the pricier model.