Kimi K3.1 Pro API pricing
Moonshot's K3.1 Pro revision. Available at listed at platform rate (no published official USD price).
| Route | Input / 1M | Output / 1M |
|---|---|---|
| Platform rate | $1 | $5 |
USD, standard tier. Rate read from the live rate config on 2026-10-31. Moonshot publishes no USD list price for this model, so nothing here is cross-checked against one — this is a gateway rate, not a discount.
Specifications
| Vendor | Moonshot |
| Context window | — |
| Max output | — |
| Category | China |
What Kimi K3.1 Pro costs at your volume
| Usage level | Input / output per month | Monthly cost |
|---|---|---|
| Light, prototyping, a few thousand calls | 5M / 1M | $10.00 |
| Working (one developer), daily use | 50M / 10M | $100.00 |
| Heavy — team or agent loops in production | 500M / 100M | $1,000.00 |
Calculated at $1 input / $5 output per 1M tokens, 5.0× apart on this model, assuming a 5:1 input-to-output ratio. That ratio is the single largest source of error in this table: resend-heavy workloads drift well past it, and at 5.0× the correction is not linear. The cost calculator takes the actual figures.
When Kimi K3.1 Pro is the right call
At $1 in and $5 out per million tokens, Kimi K3.1 Pro lands where most production deployments actually live — cheap enough to leave running, expensive enough that you still look at the bill. The 5.0× output multiple is conventional, so standard cost intuition holds: output dominates, context matters, neither is pathological.
It is not the answer at either end. Bulk classification finds identical results several times cheaper, and the hardest reasoning problems reward moving up rather than staying here. Everything in between is this model's ground.
Where Kimi K3.1 Pro sits in the index
Kimi K3.1 Pro is 151 of 226 on input rate and 162 of 226 on output rate. A gap of 11 places, because on this model the output rate is 5.0× the input rate, steeper than the index median of 4.0× An output-heavy workload therefore leaves it almost where it started, which is why the cheapest model per input token is routinely not the cheapest per task. Percentile is the share of the 226 models in this index that cost more than Kimi K3.1 Pro.
| Ranked by | Position | Percentile | Rate |
|---|---|---|---|
| Input rate | 151 of 226 | 33% | $1.00 |
| Output rate | 162 of 226 | 28% | $5.00 |
| Agent mix 1:3, blended | 168 of 226 | 26% | $4.00 |
On an agent mix the lowest blended rate in the same index is Gemma2 9B It at $0.01 per 1M tokens (about 400).0× less than this model at the same ratio. Across the whole index, sorting by input price alone moves a model by as much as 74 places; on Kimi K3.1 Pro specifically the shift is 11 — which is what the re-ranked index exists to show.
Kimi K3.1 Pro is 151 of 226 across every model in the index; the comparison that usually settles a choice is Moonshot's own lineup further down.
Kimi K3.1 Pro among Moonshot's 2 models
Kimi K3.1 Pro is the cheapest of Moonshot's 2 models in this index at $1 per 1M input tokens. The range inside that group runs from Kimi K3.1 Pro at $1 to Kimi K3 at $1.5. A spread of 2×, and every other model in the group costs more on input than this one.
| Model | In / 1M | Out / 1M | vs this |
|---|---|---|---|
| Kimi K3.1 Pro | $1 | $5 | — |
| Kimi K3 | $1.5 | $7.5 | 1.50× |
On input rate alone, stepping up to Kimi K3 costs 1.5× the input rate. Both measured at 2026-10-31, the same check as every other rate on this page.
Full Moonshot range, including models outside this shortlist: Moonshot rate index.
Similarly priced alternatives
| Similarly priced | Vendor | In / out per 1M | vs this |
|---|---|---|---|
| Claude Sonnet 5 | Anthropic | $1 / $5 | same |
| Grok 4.1 | xAI | $1 / $5 | same |
| GPT-6 Sol | OpenAI | $1 / $5 | same |
Blended comparison (input + output per 1M). Price is one axis, these are the three closest to Kimi K3.1 Pro in blended rate, not interchangeable substitutes for it.
Calling Kimi K3.1 Pro
The identifier you send is kimi-k3.1-pro. Copy it exactly, because a mismatch
returns a model error rather than a connection error, which sends most people to debug the wrong
thing. Everything else is a base URL argument, Kimi K3.1 Pro's own SDKs work unchanged.
from openai import OpenAI
client = OpenAI(base_url="https://aicomp.ai/v1", api_key="sk-...")
resp = client.chat.completions.create(
model="kimi-k3.1-pro",
messages=[
{"role": "system", "content": "Answer in one short paragraph."},
{"role": "user", "content": "Explain what changed in this release."},
],
max_tokens=300,
)
# prompt_tokens / completion_tokens 是真实账单的唯一依据 —— 记下来,别猜
print(resp.usage.prompt_tokens, resp.usage.completion_tokens)
Log the usage object on every call, not just while you are optimising. On Kimi K3.1 Pro output costs 5.0× what input costs, so the same monthly token count bills very differently depending on how much of it comes back as output — measure your own split before extrapolating from the headline input rate, because rates move with vendor promotions.
Setting it up
Pointing an existing integration at Kimi K3.1 Pro is a base URL change, not a rewrite. Pick your tool:
- Claude Code — set the base URL via environment variables
- Cursor — override the API endpoint in settings
- OpenAI / Anthropic SDK — one
base_urlargument - Python (sync), streaming and async examples
- Cutting the bill — eight levers ranked by effect
What different usage shapes cost on Kimi K3.1 Pro
A monthly token budget does not convert cleanly into a monthly invoice, and Kimi K3.1 Pro is an ordinary case rather than an extreme one: output is priced at 5.0× input, above the median of 4.0× across the 226 models in our index. Everything follows from that one number, at 5:1 it is manageable, at 1:1 the same token count costs half as much. Below are five shapes real Kimi K3.1 Pro deployments fall into, each costing it out at the split it actually produces.
| Workload | Tokens | Output share | Monthly cost | vs cheapest in index |
|---|---|---|---|---|
| Classification / tagging 100k short jobs, 300 in / 20 out | 32M | 6% | $40.00 | 34.8× |
| Support triage 20k conversations, 1.5k in / 400 out | 38M | 21% | $70.00 | 29.8× |
| RAG question answering 50k questions, 6k in / 500 out | 325M | 8% | $425.00 | 34.0× |
| Agent loop (coding) 8k sessions, 400k in / 6k out | 3248M | 1% | $3440.00 | 38.4× |
| Long-form generation 5k documents, 2k in / 4k out | 30M | 67% | $110.00 | 25.9× |
The cheapest comparison is GPT-5 nano at $0.025 / $0.2 per 1M — 26.7× cheaper than Kimi K3.1 Pro on a blended rate. Treat it as a rate floor, not a recommendation: it says nothing about whether GPT-5 nano can do the work you need Kimi K3.1 Pro for.
Read the table as a sanity check rather than a forecast. If your own output share sits anywhere near 3%, everything above is priced almost entirely at Kimi K3.1 Pro's $1 input rate; at 40% the $5 output rate has taken the larger half. Nobody's split is exactly the one you assumed when you picked the model, which is why the calculator asks for it before quoting anything.
FAQ
How much does Kimi K3.1 Pro cost per million tokens?
$1 per million input tokens and $5 per million output tokens. No official USD list price is published for this model, so it is billed at platform rate.
Is Kimi K3.1 Pro cheaper than buying direct?
There is no published official USD price to compare against for this model It is billed at platform rate, and the reason to route it through a gateway is access and consolidated billing rather than a discount.
What does Kimi K3.1 Pro cost per month in practice?
At a 5:1 input-to-output ratio it is about $10.00 a month for light use (5M input tokens) and roughly $1,000.00 for heavy use (500M input). Agent workloads sit at the high end here because every turn resends the context and Kimi K3.1 Pro bills output at 5.0x input — see what actually drives Claude Code cost.
Which models cost about the same as Kimi K3.1 Pro?
The comparison table further up this page lists the three closest to Kimi K3.1 Pro's $6 blended rate. If you are choosing on cost alone, test the top two on your own prompts — $1 per input token is only half the equation, the other half is how many tokens a model needs before it finishes the task.
How do I start using Kimi K3.1 Pro?
You need an API key, then point your client at the gateway base URL with kimi-k3.1-pro as the model id. On Kimi K3.1 Pro it is a one-line change in most SDKs — see the SDK setup guide, or the Claude Code and Cursor guides for those tools. The Kimi K3.1 Pro snippet is in the calling section above.
What is the Kimi K3.1 Pro API price per 1M tokens?
$1 per 1M input and $5 per 1M output. The two directions are quoted separately because a request is billed twice, once for what you send, once for what comes back, and on Kimi K3.1 Pro they differ by 5.0x.
How much more does Kimi K3.1 Pro charge for output than input?
Output tokens cost 5.0x what input tokens do here — $1 per 1M in against $5 per 1M out. The median output-to-input multiple across our full price index is 4.0x, so this model sits above that line. It matters more than it looks: on Kimi K3.1 Pro a coding agent's output takes 50% of the bill, so the input rate people usually compare is the smaller half. See why output pricing dominates.
How much does Kimi K3.1 Pro cost for a coding agent?
About $1,000.00 a month at 500M input and 100M output tokens (the shape a coding assistant really produces), because every turn resends the whole context and the model writes more than it reads. The biggest lever is not the model but how much context you resend each turn, at 1,000 dollars a month on Kimi K3.1 Pro, halving the resend roughly halves that. See what actually drives agent cost.
Does Kimi K3.1 Pro have an official list price?
No (Moonshot does not publish a USD list price for this model), so there is nothing to compare against and it bills at platform rate: $1 in / $5 out per 1M. The reason to route it through a gateway is access and one consolidated bill across vendors, not a discount.