Kimi K3.1 Pro Highspeed API

Kimi K3.1 Pro Highspeed is the fast variant Moonshot AI released alongside K3.1 Pro on 2026-10-23: the same model and the same benchmarks, with output Moonshot says is 2–3× faster, at $4 input / $20 output per million tokens, twice Pro. This page covers Wokey’s measured speeds, how to choose between Highspeed and Pro, Kimi Code plan limits and the request rules.

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.

ChannelInputCache readOutput
Official API$4$0.2$20
OpenRouter$4$0.2$20
Wokey$1.2$0.06$6

· 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-highspeed"

Kimi K3.1 Pro Highspeed at a glance

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
Official price
Highspeed costs $4 input / $20 output per million tokens, twice Pro ($2 / $10); cache hits stay at $0.20, and cache writes are $4 (5-minute) or $8 (1-hour)
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
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. Highspeed is the same model, so the scores are identical. Internal and cybersecurity evaluations are left out.

BenchmarkKimi K3.1 ProClaude Opus 5.5GPT-6 AstraClaude Fable 5.1GLM-5.3DeepSeek V4.1 Flash 1017
Terminal-Bench 4.065.7%66.4%58.2%57.9%41.8%42.3%
SWE-Marathon v1.151.7%46.3%42.5%45.6%42.5%40.0%
DeepSWE v1.175.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.138.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-Full51.1%59.8%53.6%57.6%43.0%42.6%
GPQA Diamond94.2%93.9%96.1%93.7%91.7%92.2%
BrowseComp92.1%90.8%91.5%———
OSWorld V2.179.6%81.8%75.8%80.7%—69.3%
OfficeQA Pro v264.4%62.2%54.4%54.5%31.1%40.4%
GDPval-AA v2.1184618661573175416501746
MMMU-Pro84.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: Highspeed or Pro, and other models

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.

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.

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.

Kimi docs

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.
  • 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 Highspeed 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-highspeed. 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 $1.20 input / $6.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-highspeed",
  "reasoning_effort": "high",
  "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-highspeed
Vendors
moonshot
Supply status
Currently callable

Catalog pricing snapshot

Prices are per 1M tokens; request-time pricing controls settlement.

MeterWokeyOfficial referenceSavings
Input$1.2$470%
Output$6$2070%
Cache read$0.06$0.270%
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-highspeed","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-highspeed","max_tokens":1024,"messages":[{"role":"user","content":"Hello"}]}'

Use Kimi K3.1 Pro Highspeed 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-highspeed. Open the guide for the client you use.

Frequently asked questions

How much faster is Kimi K3.1 Pro Highspeed than Pro?

Moonshot says 2–3×. Wokey ran the same prompt three times on each model at the Kimi Code endpoint on 10-24 (effort=high, about 2,500–3,600 output tokens): Highspeed ran 118–129 tokens/s and Pro 64–67 tokens/s, about 1.9× faster, with the first token in 3.2–3.8 seconds versus 3.9–5.2 for Pro. Speed varies with load and time of day, so measure on your own tasks.

How much does Kimi K3.1 Pro Highspeed cost, and is it worth it?

The official price is $4 input / $20 output per million tokens, twice Pro; cache hits stay at $0.20, and cache writes are $4 (5-minute) or $8 (1-hour). In Kimi Code it uses about twice the quota. It is the same model with the same benchmarks, so paying 2× for about 1.9× the speed only pays off in interactive work where someone waits on the answer. Through Wokey, kimi-k3.1-pro-highspeed costs $1.20 input / $6.00 output per million tokens (30% of the official rate), with cache reads discounted in proportion.

Which Kimi Code subscription (Coding Plan) tiers include K3.1 Pro Highspeed?

Highspeed is available on Kimi Code’s new plans from Pro up (legacy plans from Allegretto); Plus and Moderato get K3.1 Pro only. In Kimi Code the model ID is k3.1-pro-highspeed, and it uses about twice the quota of Pro; OpenCode Go does not include Highspeed. Pay-per-token access through Wokey has no plan tiers.

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.

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.

How much K3.1 Pro Highspeed 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: Highspeed uses about 52.9% of the 5-hour quota per million uncached input tokens and about 454% per million output tokens (including thinking), so one window covers roughly 1.9M uncached input tokens or about 220K output tokens. That is exactly twice K3.1 Pro (26.4% / 227%). 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% (Highspeed gets half as many tokens through a window); 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 ($4 / $20 for Highspeed), or switch to a pay-per-token API, for example kimi-k3.1-pro-highspeed through Wokey at $1.20 input / $6.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 Highspeed API cost, and how much does it save versus the official API?

Wokey lists input at $1.2 per 1M tokens and output at $6 per 1M tokens; the official references are $4 and $20. 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 Highspeed API model ID?

The model ID for Kimi K3.1 Pro Highspeed on Wokey is kimi-k3.1-pro-highspeed. 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 Highspeed support, and how do I call it through Wokey?

Kimi K3.1 Pro Highspeed 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-highspeed; 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 Highspeed in Claude Code?

Claude Code calls Kimi K3.1 Pro Highspeed 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-highspeed", 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 Highspeed?

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 Highspeed?

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 Highspeed through Wokey differ from OpenRouter?

Wokey lists Kimi K3.1 Pro Highspeed at $1.2 input / $6 output per 1M tokens, against an official reference of $4 / $20. 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 Highspeed and Kimi K3.1 Pro differ in price and context?

In the published price comparison, Kimi K3.1 Pro Highspeed lists input/output at $1.2 / $6 with a 1,048,576-token context window; Kimi K3.1 Pro lists $0.6 / $3 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-highspeed