Kimi K3.1 Pro API
Kimi K3.1 Pro is the post-trained K3 that Moonshot AI released on 2026-10-23, with 2.8T total and 104B active parameters, a 1M context window and native image and video input. It lists at $2 input / $10 output per million tokens, a third below K3. This page covers the official and third-party benchmarks, how it compares with Claude Opus 5.5, K3 and GLM-5.3, how much faster the Highspeed variant really is, which Kimi Code plans include it, the request errors and limits, and Wokey API key pricing and examples.
Price check: official, OpenRouter and Wokey
USD per million tokens. Official and OpenRouter rates were checked by hand on 2026-10-24, excluding tax; the Wokey rate is read from the live price list.
| Channel | Input | Cache read | Output |
|---|---|---|---|
| Official API | $2 | $0.2 | $10 |
| OpenRouter | $2 | $0.2 | $10 |
| Wokey | $0.6 | $0.06 | $3 |
· Official pricing page · OpenRouter endpoint list
Use it in Claude Code
This model supports /v1/messages on Wokey. Set these variables, then start claude.
export ANTHROPIC_BASE_URL="https://api.wokey.ai"
export ANTHROPIC_AUTH_TOKEN="$WOKEY_API_KEY"
export ANTHROPIC_MODEL="kimi-k3.1-pro"Kimi K3.1 Pro at a glance
- Release date
- 2026-10-23: K3.1 Pro and K3.1 Pro Highspeed shipped on the Kimi web app and mobile apps, Kimi Work, Kimi Code and the Kimi API on day one; Moonshot promises the full weights on Hugging Face by November 4
- Model
- A post-trained K3: the same 2.8T-total, 104B-active MoE base with far more reinforcement-learning post-training compute; 1,048,576-token context with native text, image and video input
- Official price
- K3.1 Pro costs $2 input / $10 output per million tokens, $0.20 for cache hits, and $2 (5-minute) or $4 (1-hour) for cache writes, a third below K3 ($3 / $15). Highspeed doubles input, output and writes ($4 / $20) but keeps cache hits at $0.20
- Highspeed
- The same model, which Moonshot says runs 2–3× faster. Wokey measured on 10-24 (Kimi Code endpoint, effort=high): Pro 64–67 tokens/s, Highspeed 118–129 tokens/s, about 1.9× faster; K3 ran about 45 tokens/s under the same conditions
- Thinking and parameters
- Thinking-only: disabling thinking returns 400. reasoning_effort accepts low / high / max with max as the default; temperature, top_p and the other sampling parameters are fixed, the same constraints as K3
- Independent evaluation
- Artificial Analysis Intelligence Index v4.3.2: 55, ranked 4 of 215, behind only Claude Opus 5.5 (58), Sonnet 5.5 (56) and Muse Wonder Full (56), and 11 points above K3; $2.11 per task, about a third of Opus 5.5
- API and channels
- Model IDs are kimi-k3.1-pro and kimi-k3.1-pro-highspeed on the Kimi platform, and k3.1-pro and k3.1-pro-highspeed in Kimi Code. Wokey serves /v1/chat/completions and /v1/messages (works with Claude Code)
· Sources: Moonshot · K3.1 Pro quickstart · Pricing · Kimi Code models · Artificial Analysis
Official benchmarks: Kimi K3.1 Pro vs Opus 5.5 vs GPT-6 Astra vs Fable 5.1 vs GLM-5.3 vs DeepSeek
From Moonshot’s K3.1 Pro tech blog; these are vendor-reported results, and “—” means no score was published. Internal and cybersecurity evaluations are left out.
| Benchmark | Kimi K3.1 Pro | Claude Opus 5.5 | GPT-6 Astra | Claude Fable 5.1 | GLM-5.3 | DeepSeek V4.1 Flash 1017 |
|---|---|---|---|---|---|---|
| Terminal-Bench 4.0 | 65.7% | 66.4% | 58.2% | 57.9% | 41.8% | 42.3% |
| SWE-Marathon v1.1 | 51.7% | 46.3% | 42.5% | 45.6% | 42.5% | 40.0% |
| DeepSWE v1.1 | 75.5% | 74.2% | 74.1% | 67.4% | 66.9% | 77.0% |
| ProgramBench (binary) | 31.5% | 65.0% | 50.0% | 53.5% | 19.0% | 29.1% |
| Terminal-Bench Science 0.1 | 38.1% | 63.3% | 68.1% | 40.0% | 8.1% | 15.7% |
| BenchCAD (tools) | 92.7% | 96.2% | 95.9% | 92.6% | — | 81.6% |
| HLE-Full (tools) | 70.0% | 67.7% | 57.2% | 65.6% | 62.5% | 58.8% |
| HLE-Full | 51.1% | 59.8% | 53.6% | 57.6% | 43.0% | 42.6% |
| GPQA Diamond | 94.2% | 93.9% | 96.1% | 93.7% | 91.7% | 92.2% |
| BrowseComp | 92.1% | 90.8% | 91.5% | — | — | — |
| OSWorld V2.1 | 79.6% | 81.8% | 75.8% | 80.7% | — | 69.3% |
| OfficeQA Pro v2 | 64.4% | 62.2% | 54.4% | 54.5% | 31.1% | 40.4% |
| GDPval-AA v2.1 | 1846 | 1866 | 1573 | 1754 | 1650 | 1746 |
| MMMU-Pro | 84.1% | 87.7% | 86.9% | 86.3% | — | 80.6% |
Every K3.1 Pro score uses reasoning_effort=max, temperature=1.0 and top_p=0.95, with coding benchmarks in the Claude Code harness; the three proprietary models ran at max with fallback. The ProgramBench row is a binary score (a task counts when it reaches ≥95%), so it is not comparable with the raw scores on the K3 page. GLM-5.3’s HLE-Full score is on the text-only subset.
Which to use: K3.1 Pro, Claude Opus 5.5, K3 or GLM-5.3
vs Claude Opus 5.5
On Artificial Analysis’ Intelligence Index v4.3.2 Opus 5.5 (max) scores 58 and K3.1 Pro 55, only 3 points apart, while a task costs $5.98 versus $2.11, about a third for K3.1 Pro. Moonshot’s table has them nearly level on Terminal-Bench 4.0 (65.7% vs 66.4%), and tbench.ai’s cost data puts a task at about $5.25 for K3.1 Pro and $14.30 for Opus 5.5. K3.1 Pro leads on SWE-Marathon v1.1 (51.7% vs 46.3%), HLE with tools (70.0% vs 67.7%) and OfficeQA Pro v2; Opus 5.5 is clearly stronger on ProgramBench (65.0% vs 31.5%), Terminal-Bench Science (63.3% vs 38.1%) and HLE without tools (59.8% vs 51.1%), and faster (about 96 vs 77 tokens/s). Pick K3.1 Pro for long-horizon coding agents, document and finance analysis, and budget-sensitive volume; pick Opus 5.5 for complex programs that must work first time and for scientific work.
Upgrading from K3
Yes, for pay-per-token API use. K3.1 Pro scores 11 points higher than K3 on the index (55 vs 44), lists a third cheaper, and outputs about 64–67 tokens/s against K3’s 45 in Wokey’s measurements. The request constraints are the same as K3’s, so switching is a matter of changing model from kimi-k3 to kimi-k3.1-pro. Kimi recommends starting a new session: switching mid-way through a K3 session invalidates the cache and can lower output quality. Kimi Code subscribers should note that, in Wokey’s measurement on the Max plan, K3.1 Pro uses about 50% more quota on input and 82% more on output than K3 for the same tokens, so keep simple tasks on K3 when quota is tight.
vs GLM-5.3 and DeepSeek V4.1 Flash
Both score 45 on Artificial Analysis, 10 points below K3.1 Pro. GLM-5.3 costs $2.01 per task, almost the same as K3.1 Pro’s $2.11, so at the same spend K3.1 Pro is clearly stronger and also takes images and video. DeepSeek V4.1 Flash 1017 costs only $0.26 per task, about an eighth of K3.1 Pro, and even edges it on DeepSWE (77.0% vs 75.5%), but scores only 42.3% on Terminal-Bench 4.0. Use DeepSeek for simple high-volume work and K3.1 Pro for complex agentic and multimodal tasks.
Pro or Highspeed
They are the same model with the same benchmark scores. Highspeed costs twice as much and uses about twice the quota in Kimi Code; in Wokey’s measurements it is about 1.9× faster (118–129 vs 64–67 tokens/s) and reaches the first token about a second sooner. Choose Highspeed for interactive coding where someone waits on the answer; choose Pro for background agents, batch work and token-budgeted jobs.
Choosing effort
Thinking cannot be turned off, and reasoning_effort accepts only low, high and max, with max as the default. On the Terminal-Bench 4.0 cost curve Moonshot published, high scores 52.8% at about $4.16 per task and max 65.7% at about $5.25: max costs 26% more for 12.9 more points. Keep max for coding and agents and use low for simple Q&A and format conversion. Reasoning tokens bill at the output rate, and Artificial Analysis recorded 150M output tokens across its index, 70% above the 87M median, so leave room in output budgets.
Third-party and community reviews
- Artificial Analysis: Intelligence Index v4.3.2: 55, ranked 4 of 215. It used 150M output tokens across the index (median 87M), costs $2.11 per task, outputs about 77 tokens/s and takes about 3.1 seconds to first token. It is listed as proprietary until the weights ship. Every Wokey meter is 30% of the official rate, so the same task comes to about $0.63.
- Hacker News (542-point thread): The most discussed point was Moonshot removing cybersecurity material from the training data: some see it as sturdier than refusals, others worry about general coding skill. Next came Kimi’s subscription quota: one user on the $99 tier used up the 5-hour quota in 47 minutes of one session. Others noted the China price is about 30% below K3 and that it now ranks above GPT-6 Astra and Fable 5.1 on Artificial Analysis.
- Wokey measurements: On 10-24 Wokey ran the same prompt (a technical write-up of about 900 words) three times per model at the Kimi Code endpoint (effort=high): K3.1 Pro ran 64–67 tokens/s, Highspeed 118–129 tokens/s and K3 about 45 tokens/s. Both chat/completions and the messages format Claude Code uses return thinking normally; disabling thinking, top_p≠0.95 and public image URLs all return 400.
Using K3.1 Pro in Claude Code, and request rules to check
These rules come from Kimi’s documentation and Wokey’s tests of both models on 10-24. Check them before switching from K3 or wiring it up for the first time.
- Model IDs: the Kimi platform and Wokey use kimi-k3.1-pro / kimi-k3.1-pro-highspeed; keys from a Kimi Code membership need k3.1-pro / k3.1-pro-highspeed. In Wokey’s test, sending kimi-k3.1-pro to Kimi Code returns 400 “Your model id does not exist”.
- Thinking cannot be turned off: thinking: {"type": "disabled"} returns 400 “K3.1 Pro does not support disabled thinking mode”. Use the top-level reasoning_effort (low / high / max) to control how much it thinks.
- temperature, top_p, n, presence_penalty and frequency_penalty are fixed at 1.0, 0.95, 1, 0 and 0, and Kimi asks you to omit them; top_p=1 returns 400 “invalid top_p: only 0.95 is allowed for this model”. The Wokey gateway enforces the same rules, so the answer does not depend on which upstream serves the request.
- In multi-turn chats and tool calls, pass back the complete assistant message the API returned, including reasoning_content and tool_calls.
- Images go in as base64 data URLs such as data:image/png;base64,.... In Wokey’s 10-24 test a public image URL returned 400 “unsupported image url”, as with K3; video also goes in as base64.
- In Claude Code: set ANTHROPIC_BASE_URL to https://api.wokey.ai, ANTHROPIC_AUTH_TOKEN to your Wokey API key and ANTHROPIC_MODEL to kimi-k3.1-pro. Wokey tested both models on 10-24 in the /v1/messages format Claude Code uses, and thinking blocks and text came back normally; it costs $0.60 input / $3.00 output per million tokens. OpenCode and other OpenAI-compatible clients use /v1/chat/completions with the base URL https://api.wokey.ai/v1.
Request body with an image (/v1/chat/completions)
{
"model": "kimi-k3.1-pro",
"reasoning_effort": "max",
"messages": [{
"role": "user",
"content": [
{ "type": "image_url", "image_url": { "url": "data:image/png;base64,iVBORw0KGgo..." } },
{ "type": "text", "text": "Rebuild this CAD sketch as a parametric Blender script" }
]
}]
}- Model ID
kimi-k3.1-pro- Vendors
- moonshot
- Supply status
- Currently callable
Catalog pricing snapshot
Prices are per 1M tokens; request-time pricing controls settlement.
| Meter | Wokey | Official reference | Savings |
|---|---|---|---|
| Input | $0.6 | $2 | 70% |
| Output | $3 | $10 | 70% |
| Cache read | $0.06 | $0.2 | 70% |
| Cache write | — | — | — |
Official price source: https://platform.kimi.ai/docs/pricing/chat
Model capabilities
- Context
- 1,048,576 tokens
- Max output
- 1,048,576 tokens
- Streaming
- Supported
- Tools
- Supported
- Vision
- Supported
- Supported API forms
/v1/chat/completions·/v1/messages
Send a request
/v1/chat/completions
curl https://api.wokey.ai/v1/chat/completions \
-H "Authorization: Bearer $WOKEY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"kimi-k3.1-pro","messages":[{"role":"user","content":"Hello"}]}'/v1/messages
curl https://api.wokey.ai/v1/messages \
-H "x-api-key: $WOKEY_API_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "Content-Type: application/json" \
-d '{"model":"kimi-k3.1-pro","max_tokens":1024,"messages":[{"role":"user","content":"Hello"}]}'Use Kimi K3.1 Pro in your tools
The gateway is https://api.wokey.ai (OpenAI-compatible clients usually take https://api.wokey.ai/v1), and the model ID is kimi-k3.1-pro. Open the guide for the client you use.
- Use Kimi K3.1 Pro in Claude Code: Anthropic Messages · base URL and API key setup
- Use Kimi K3.1 Pro in Claude Desktop: Anthropic Messages · base URL and API key setup
- Use Kimi K3.1 Pro in opencode: OpenAI Chat Completions · base URL and API key setup
- Use Kimi K3.1 Pro in OpenClaw: OpenAI Chat Completions · base URL and API key setup
- Use Kimi K3.1 Pro in Hermes Agent: OpenAI Chat Completions · base URL and API key setup
- Use Kimi K3.1 Pro in DeepSeek Harness: OpenAI Chat Completions · base URL and API key setup
- Kimi Code limits, measured: how much Kimi K3.1 Pro a plan covers: Measured tokens per 5-hour window and per month, and what they are worth at API prices.
- OpenRouter alternative: Wokey vs OpenRouter: Compare token prices, payment fees, API forms, and upstream sources.
- Verifiable AI API: which models and API forms carry response proofs: Response proofs currently cover only raw passthrough Claude Messages and GPT Responses on official routes.
Frequently asked questions
What is Kimi K3.1 Pro’s official pricing, and how much cheaper is it than K3?
The official price is $2 input / $10 output per million tokens, $0.20 for cache hits and $2 (5-minute) or $4 (1-hour) for cache writes, with no context-length tiers. That is a third below K3 ($3 / $15). Highspeed costs $4 / $20, with cache hits still at $0.20. Reasoning tokens bill at the output rate. On OpenRouter, Moonshot is currently the only provider, at the official price. Through Wokey, kimi-k3.1-pro costs $0.60 input / $3.00 output per million tokens (30% of the official rate), with cache reads discounted in proportion.
Kimi K3.1 Pro vs Claude Opus 5.5: which is better?
On Artificial Analysis’ Intelligence Index v4.3.2 Opus 5.5 scores 58 and K3.1 Pro 55, just 3 points apart, but a task costs $5.98 versus $2.11, about a third for K3.1 Pro. They are nearly level on Terminal-Bench 4.0 (66.4% vs 65.7%); K3.1 Pro leads on SWE-Marathon and HLE with tools, while Opus 5.5 is clearly stronger on ProgramBench and scientific work and runs faster. Pick K3.1 Pro for budget-conscious long-horizon agents and Opus 5.5 for complex programs that must work first time.
What is the difference between Kimi K3.1 Pro and K3?
K3.1 Pro is a post-trained K3 of the same size (2.8T total, 104B active parameters) with far more post-training compute. Its Artificial Analysis index rose from 44 to 55, the official price fell from $3 / $15 to $2 / $10, output speed in Wokey’s measurements rose from about 45 to 64–67 tokens/s, and on Moonshot’s internal hallucination test the claim-level hallucination rate fell from 23.4% to 8.3%. The request constraints are unchanged: switch model to kimi-k3.1-pro and start a new session. Kimi Code subscribers should note that, in Wokey’s measurement on the Max plan, K3.1 Pro uses about 50% more quota on input and 82% more on output than K3 for the same tokens, so keep simple tasks on K3 when quota is tight.
Where does Kimi K3.1 Pro rank on Artificial Analysis?
On Intelligence Index v4.3.2 K3.1 Pro scores 55, ranked 4 of 215, behind only Claude Opus 5.5 (58), Claude Sonnet 5.5 (56) and Muse Wonder Full (56). It is ahead of GPT-6 Astra (53) and Claude Fable 5.1, and 10 points above the open GLM-5.3 and DeepSeek V4.1 Flash (both 45). It used 150M output tokens across the index, so it is verbose; a task costs $2.11 and it outputs about 77 tokens/s. At Wokey’s prices the same task costs about $0.63.
Is Kimi K3.1 Pro open source, and when will the weights be on Hugging Face?
Moonshot promises the full weights on Hugging Face by November 4, 2026; they were not out as of 10-24, which is why Artificial Analysis lists it as proprietary for now. K3.1 Pro uses K3’s architecture (2.8T total, 104B active), so K3 is a guide to the hardware: its native MXFP4 weights are about 1.56 TB, and vLLM’s official recipe needs at least 8 GB300 or 8 MI355X/MI350X GPUs in one node. Until the weights ship, the API is the only way to use it.
Which Kimi Code subscription (Coding Plan) tiers include K3.1 Pro, and is the quota enough?
Kimi Code’s new plans include K3.1 Pro from Plus up (legacy plans from Moderato), but the 1M context needs Pro or above (legacy: Allegretto or above), and Highspeed is limited to Pro and above at about twice the quota. Quotas are capped by a 5-hour window and a monthly total; one Hacker News user on the $99 tier used up the 5-hour quota in 47 minutes of a single session. For heavy use or steady throughput, a pay-per-token API is easier to plan around.
Why does Kimi K3.1 Pro return “does not support disabled thinking mode”?
K3.1 Pro and Highspeed run in thinking mode only, so a request with thinking: {"type": "disabled"} returns 400 “K3.1 Pro does not support disabled thinking mode”. Remove the thinking parameter and lower the thinking with reasoning_effort: "low"; if you need no thinking at all, use a different model.
Is Kimi K3.1 Pro on OpenCode Go, and how much usage do you get?
Yes. OpenCode Go includes kimi-k3.1-pro (served on Chat Completions), with usage counted at the official $2 / $10: Go ($10/month) gives K3.1 Pro $15 a month, which OpenCode estimates at about 147 requests per 5 hours and 735 per month; Go Plus ($40/month) gives $60, about 2,941 requests per month. The 5-hour window is 20% of the monthly limit and the week 50%. Highspeed is not in Go’s model list. You can also add a custom OpenAI-compatible provider in OpenCode with the base URL https://api.wokey.ai/v1 and model kimi-k3.1-pro, paying per token ($0.60 input / $3.00 output per million tokens).
How much K3.1 Pro fits in one 5-hour window on Kimi Code Max (¥699)?
Wokey measured this on a Kimi Code Max key (new plan) on 10-24: K3.1 Pro uses about 26.4% of the 5-hour quota per million uncached input tokens and about 227% per million output tokens (including thinking), so one window covers roughly 3.8M uncached input tokens or about 441K output tokens. Highspeed uses exactly twice as much. For the same tokens K3.1 Pro uses about 50% more quota than K3 on input and 82% more on output, even though its API price is a third lower. Cache hits barely count (45K cached tokens did not move the reading) and the first cache write counts as normal input, so avoid restarting long sessions. The monthly total is about 25 five-hour windows. At K3.1 Pro’s official API price one window is worth about $7.6 of pure input or $4.4 of pure output, about $14 for a coding session with 93% cache hits and about $25 at 99%; the widely shared “$25 per 5 hours” only holds with very high cache share. Other plans’ window sizes were not measured.
Kimi Code says “You’ve reached your 5-hour usage limit”: what now?
Kimi Code’s rolling 5-hour quota is used up, and the API returns 429: “You’ve reached your 5-hour usage limit. Your quota will reset when the current 5-hour window ends.” Retrying does not help; wait for the window to roll over, and the Kimi Code console shows when. Since October 2026 the new plans (Plus and above) have no weekly quota, but the 5-hour window and the monthly total shared with the Kimi web app remain, and running out of the monthly total freezes access until it refreshes. To keep going you can upgrade, turn on Extra Usage, which bills by use at what Kimi calls close to its API price ($2 / $10 for K3.1 Pro), or switch to a pay-per-token API, for example kimi-k3.1-pro through Wokey at $0.60 input / $3.00 output per million tokens with no 5-hour window. Highspeed uses about twice the quota of Pro, so switch back to Pro when quota is tight.
How much does the Kimi K3.1 Pro API cost, and how much does it save versus the official API?
Wokey lists input at $0.6 per 1M tokens and output at $3 per 1M tokens; the official references are $2 and $10. That is 70% lower for input and 70% lower for output. Request-time pricing controls settlement, and the vendor pricing source is linked on this page.
What is the Kimi K3.1 Pro API model ID?
The model ID for Kimi K3.1 Pro on Wokey is kimi-k3.1-pro. Use it exactly as written in the request body's model field or in your client's model setting (for example ANTHROPIC_MODEL in Claude Code, or model in the Codex CLI config.toml); GET https://api.wokey.ai/v1/models also lists it.
Which API forms does Kimi K3.1 Pro support, and how do I call it through Wokey?
Kimi K3.1 Pro supports /v1/chat/completions (Chat Completions requests) and /v1/messages (Messages requests). Set the API base URL to https://api.wokey.ai, authenticate with a Wokey API key, and use the canonical model ID kimi-k3.1-pro; you can start with /v1/chat/completions. The Send a request section includes a curl example for every supported API form.
How do I use Kimi K3.1 Pro in Claude Code?
Claude Code calls Kimi K3.1 Pro over /v1/messages. Set ANTHROPIC_BASE_URL="https://api.wokey.ai", ANTHROPIC_AUTH_TOKEN to your Wokey API key, and ANTHROPIC_MODEL="kimi-k3.1-pro", then start claude. Claude Desktop also uses /v1/messages; the setup guides cover both step by step.
What are the context window and maximum output for Kimi K3.1 Pro?
The catalog context window is 1,048,576 tokens and the maximum output is 1,048,576 tokens. These are separate limits, and a request must also satisfy the upstream constraints in effect when it is processed.
How are cache reads and cache writes priced for Kimi K3.1 Pro?
Cache read: Wokey lists $0.06 per 1M tokens and the official reference is $0.2 per 1M tokens. Cache write: the vendor does not publish a separate meter, so Wokey also shows — as the public price.
How does calling Kimi K3.1 Pro through Wokey differ from OpenRouter?
Wokey lists Kimi K3.1 Pro at $0.6 input / $3 output per 1M tokens, against an official reference of $2 / $10. OpenRouter states it adds no markup on inference and charges its fee when you buy credits (5.5% by card). Wokey carries a curated set of models and has no per-provider routing parameters, so OpenRouter fits better if you need a wider catalog. The OpenRouter alternative page has the full comparison.
How do Kimi K3.1 Pro and Kimi K3.1 Pro Highspeed differ in price and context?
In the published price comparison, Kimi K3.1 Pro lists input/output at $0.6 / $3 with a 1,048,576-token context window; Kimi K3.1 Pro Highspeed lists $1.2 / $6 with a 1,048,576-token context window. This is a factual price-and-capacity comparison, not a quality ranking; also compare their supported API forms and capabilities.
Related models and documentation
Get API key · kimi-k3.1-pro