
Key Takeaways
- Moonshot AI released Kimi K3.1 Pro on October 23, 2026, with a 1-million-token context window and a faster Highspeed option.
- Kimi K3.1 Pro builds on K3 through additional post-training, rather than an entirely new base-model architecture.
- Artificial Analysis scored Kimi K3.1 Pro 55 on its Intelligence Index, while reporting below-median output speed and relatively high token usage.
- Kimi K3.1 Pro costs $2 per million input tokens and $10 per million output tokens through the first-party API.
- Moonshot plans to publish the full Kimi K3.1 Pro model weights by November 4, 2026; license terms remain unconfirmed.
Kimi K3.1 Pro is a substantial improvement in agent-driven coding and tool-based work, but its most important limitation is not model size. Strong benchmark scores do not automatically translate into fast, inexpensive, or reliable completion of a specific user's task. The useful question is whether the new model finishes a workflow accurately enough to justify its thinking time, output tokens, and supervision.
The technical distinction starts with what Moonshot actually released.
Kimi K3.1 Pro is a large, reasoning-oriented language model from Moonshot AI, released on October 23, 2026 as the first K3.1-series model. The model combines a roughly 2.8-trillion-parameter mixture-of-experts architecture, approximately 104 billion active parameters, and up to 1,048,576 tokens of context with post-training designed for multi-step, tool-using tasks.
That specification describes the underlying model, not the amount of context or execution time every Kimi subscription includes. A large context window establishes capacity; accuracy, tool permissions, and usage limits determine what a person can actually finish with it.
What Is Kimi K3.1 Pro?
Kimi K3.1 Pro is Moonshot AI's new flagship reasoning model, built through a more intensive post-training process on top of Kimi K3. The model accepts text and visual information, produces text output, and is offered through Kimi's consumer services and developer interfaces. Its primary focus is longer sequences of decisions, code execution, research, and tool use rather than ordinary short-form chatting.
Kimi K3.1 Pro at a Glance
|
Specification |
Kimi K3.1 Pro |
What the number means |
|---|---|---|
|
Released |
October 23, 2026 |
Available via hosted Kimi services |
|
Model scale |
3T-class; about 2.8T total parameters |
Total expert capacity, not per-token computation |
|
Active parameters |
About 104B |
Approximate parameters used per token in its MoE design |
|
Maximum context |
1,048,576 tokens |
Product- and plan-level limits may be lower |
|
Input / output |
Text and images; some Kimi Code clients also accept video / text output |
Modality support varies by interface |
|
Reasoning |
Low, high, or max; cannot be disabled |
Thinking consumes time and output tokens |
|
Main versions |
K3.1 Pro; K3.1 Pro Highspeed |
Claimed quality parity, different latency and cost |
|
Weights |
Promised by November 4, 2026 |
Not yet a downloadable release on October 27 |
The active-parameter figure matters because Kimi K3.1 Pro is not running all 2.8 trillion parameters for every token. In a mixture-of-experts model, selected experts perform work for a given token while the full model retains a much larger pool of learned capacity. Parameter count alone is a weak predictor of response quality, infrastructure cost, or inference speed.
The release also introduces an important naming distinction. Kimi is the consumer-facing product family; K3.1 Pro is the underlying model. Kimi Code, Kimi Work, and Kimi's general web interface expose different tools and permissions around that model. A model that can propose a modification cannot automatically edit a repository or access a private spreadsheet unless the surrounding application provides the required tools.
Moonshot describes these changes in its official K3.1 Pro technical report, published for the October 2026 launch. The report supplies engineering details and vendor-run benchmarks; the latter still need independent interpretation.
What's New in Kimi K3.1 Pro Compared With K3?
K3.1 Pro's central change is stronger post-training rather than a newly trained 3T base model. Moonshot says it invested more compute into reinforcement learning across hundreds of downstream domains, including training environments, long-context inference, tool-use rollouts, and quality checks. More training after pretraining can change how a model plans, recovers from failed attempts, and decides when to use tools, even when the base architecture remains comparable.
Kimi K3 vs K3.1 Pro: Key Differences
|
Question |
Kimi K3 |
Kimi K3.1 Pro |
|---|---|---|
|
Foundation |
Previous 2.8T-class flagship |
Post-trained successor built on K3 |
|
Long-context ceiling |
Up to 1M tokens in supported services |
Up to 1M tokens in supported services |
|
Independent Intelligence Index |
About 44 |
About 55 |
|
Independent Terminal-Bench 4.0 |
About 13% |
About 67% |
|
Standard API input / output |
$3 / $15 per 1M tokens |
$2 / $10 per 1M tokens |
|
Key change |
Strong general and agent abilities |
Larger gains on tool-driven, multi-step work |
The independent figures reflect Artificial Analysis's October 2026 measurements, not Moonshot's internal scorecard. K3.1 Pro's roughly 11-point gain on the composite Intelligence Index is meaningful, but the pattern is uneven: the improvement is especially pronounced in terminal-based agent tasks, with smaller gains on some scientific and knowledge evaluations.

An agent-heavy improvement should not be confused with a universal increase in factual reliability. The K3.1 Pro launch is about getting more multi-stage work done. Readers interested in the contrasting architecture of specialized AI decision models can compare tools that produce bounded decisions against large generative models that must plan and act across many steps.
Kimi K3.1 Pro vs Highspeed
K3.1 Pro Highspeed is a faster service tier for the same model capability. Moonshot advertises approximately two to three times the speed, while its Kimi Code membership documentation states that Highspeed consumes roughly twice the usage quota of the regular version. Through the international API price listing, the Highspeed model is approximately $4 per million input tokens and $20 per million output tokens, versus $2 and $10 for standard K3.1 Pro.
Speed is not the same as task throughput. Faster token emission may help interactive coding, but tool calls, browser latency, file execution, and total reasoning-token consumption can dominate completion time. Highspeed is easier to justify for a user waiting on iterative responses than for a batch job running unattended overnight. A cautious comparison holds the task, reasoning setting, tools, and output requirements constant.
How Good Is Kimi K3.1 Pro? Benchmarks vs Real-World Performance
The clearest sign of K3.1 Pro's progress comes from agent benchmarks. The important distinction is between Moonshot's vendor-run results, an external evaluator using a separate harness, and an actual deployment with permissions, deadlines, and failure recovery. Those are three different layers of evidence.
A useful benchmark needs an owner, a reproducible setup, and an explicitly defined success criterion.
Kimi K3.1 Pro recorded a 65.7% Terminal-Bench 4.0 score in Moonshot AI's Claude-Code-harness evaluation, compared with approximately 67% in Artificial Analysis's independent testing. The two results come from different execution configurations. Artificial Analysis reported an Intelligence Index score of 55 and 73.5 output tokens per second in its snapshot.
The results are consistent enough to support a strong agentic-coding signal. They do not establish the model's reliability on an unfamiliar company's codebase, where tests, dependencies, secrets, and tool limits differ from benchmark conditions.
Moonshot's Published Benchmark Results
Moonshot reports K3.1 Pro at 61.2% on its internal Kimi Code Bench 3.0 Long-horizon, versus 55.95% for K3. On BenchCAD's tool-enabled 3D reconstruction evaluation, it reports 92.7% for K3.1 Pro, behind Claude Opus 5.5 at 96.2% and GPT-6 Astra at 95.9% in the stated evaluation. Those comparisons are informative primarily as evidence of which workloads the developer optimized.
Moonshot also reports a claim-level hallucination rate of 8.3% for K3.1 Pro and 23.4% for K3 on its deliberately difficult Kimi Hallu Bench Hard set. The developer explicitly cautions that this is a stress test rather than an everyday error rate. Presenting 8.3% as the model's universal probability of hallucinating would be incorrect.

What Independent Benchmarks Actually Show
Artificial Analysis's independent Kimi performance measurements place K3.1 Pro at 55 on its Intelligence Index and report roughly 67% on Terminal-Bench 4.0. The assessment also records 73% on AutomationBench-AA, 1,846 Elo on GDPval-AA v2.1, and 52% on Humanity's Last Exam in its October 2026 comparison data.
The performance has a cost dimension. Artificial Analysis's model-page snapshot lists $2.11 per Intelligence Index task, around 73.5 output tokens per second, and approximately 150 million generated output tokens across its Index evaluation against a peer median of 87 million. These are evaluator-specific measurements, not promises about the response time or cost of every customer request. A detailed coding run can consume extensive reasoning output even when the visible final answer is concise.
The independent testing also exposes a less flattering side. Artificial Analysis characterizes K3.1 Pro as relatively verbose and below its comparison median for output speed. Strong task success with extra reasoning or waiting may be the right trade for difficult jobs, but the trade matters for high-volume applications where seconds and token budgets compound.
Where Benchmark Comparisons Can Mislead
Benchmark percentages are not exchangeable currencies. Two evaluations labeled Terminal-Bench can use different agent harnesses, permitted tools, retry strategies, effort settings, and time budgets. Moonshot's published K3.1 Pro comparisons generally use maximum reasoning effort, while some competitor values come from separate vendors or leaderboards. The reported margin can therefore reflect more than the model weights.
The more useful procurement test is a paired workflow trial: provide the same real tasks, repository access, tool permissions, deadline, and acceptance tests to both systems. Measure successful completions, human corrections, median and worst-case turnaround time, total billed tokens, and whether the model accurately admits failure. A high public score is a reason to shortlist the model, not sufficient evidence to migrate a production workflow.
What Can Kimi K3.1 Pro Actually Do?
K3.1 Pro is most relevant when the work requires multiple decisions and external actions. The model itself does not supply every application-specific capability; an agent environment provides repository tools, file operations, browsing, or other integrations, and the model decides how to use them.
Coding and Long-Horizon Agents
Coding tasks are the strongest documented use case. Moonshot demonstrates multi-file work, game-engine development, and tool-driven iteration. One company-run demonstration used an anatomical simulation and repeated experiment cycles to improve a virtual walking controller. These demonstrations show feasibility under a prepared environment; they do not prove that similar results are guaranteed on arbitrary projects.
A credible coding trial should contain more than code completion. Give K3.1 Pro a failing unit test, an ambiguous bug report, and a repository it has not seen before. Check whether it changes only the necessary files, runs tests rather than inventing results, reports any blocked dependencies, and explains the final patch. Agent reliability is visible in the failure path, not just the successful demo.
Readers who primarily need a ready-made task executor rather than a model API should compare personal AI agent tools on permissions, supported apps, confirmation mechanisms, and verifiable completion. The model and the product wrapped around it answer different purchasing questions.
3D Modeling and Kimi 3D Make
Moonshot has made 3D creation a flagship feature of the release. Kimi 3D Make can preview and edit models online, with export options for assets and 3D printing according to the October 2026 launch materials. K3.1 Pro can also generate scripts for Blender or CAD workflows and operate tools when the environment allows it.

A good-looking viewport is not a mechanical validation. A 3D object intended for printing or manufacturing still needs checks for scale, mesh integrity, tolerances, geometry, and material suitability. The correct question is whether the exported asset meets the target application's constraints, not whether the promotional render looks polished.
Financial Research and Document Analysis
Financial research offers a second plausible strength. Moonshot cites 64.4 on OfficeQA Pro v2 and reports internal improvements in financial modeling and research, including an 11.6-point gain on its research benchmark over K3. Those figures describe tested datasets and specific harnesses, not a guarantee that K3.1 Pro can validate every balance sheet or investment claim.
A defensible financial workflow requires the model to identify filing dates, separate reported figures from calculations, retain source-page references, and expose formulas or intermediate arithmetic. A useful test combines conflicting disclosures from different quarters and asks the model to explain the difference rather than choose an unsupported number. Human verification remains necessary when financial decisions or regulatory reporting depend on the output.
Kimi K3.1 Pro Pricing and How to Access It
Token price is only the first line of an AI-model budget. K3.1 Pro's large context window and mandatory reasoning mode can change total spend substantially, particularly when an agent repeatedly sends prior messages and produces long internal reasoning trajectories.
The useful unit of comparison is cost per verified result, not cost per advertised million tokens.
Kimi K3.1 Pro's first-party USD API rate is $2 per million uncached input tokens and $10 per million output tokens; cached input is listed at $0.20 per million tokens. Highspeed costs approximately twice the standard input and output rates. Actual cost depends on caching, reasoning tokens, retries, tool calls, and successful completions.
That is why a nominally cheaper model can cost more to operate. A second attempt after a failed run, or a large reasoning trace that does not improve the final artifact, can erase the advantage of a lower token tariff.

API Pricing: Standard vs Highspeed vs K3
|
Hosted API model |
Input / 1M tokens |
Output / 1M tokens |
When to consider it |
|---|---|---|---|
|
Kimi K3.1 Pro |
$2 |
$10 |
Cost-sensitive reasoning and agent work |
|
Kimi K3.1 Pro Highspeed |
Approx. $4 |
Approx. $20 |
Interactive workflows where speed matters |
|
Kimi K3 |
$3 |
$15 |
Existing integrations requiring K3 behavior |
These USD rates describe the international first-party API context; local-market pricing, subscription access, cache writes, and applicable taxes may differ. Highspeed's doubled rates should not be extrapolated into a fixed doubled bill when prompt caching and generated-token volumes change. The earlier K3 rate is included for like-for-like direction, not as an assurance that a legacy endpoint will remain unchanged.
A simple illustrative calculation makes the distinction concrete. A K3.1 Pro call with 100,000 uncached input tokens and 20,000 output tokens costs about $0.40 before taxes and other billable events: $0.20 for input plus $0.20 for output. Ten repeated attempts with the same uncached usage would be about $4.00. A real agent can make multiple calls with different cache behavior, so the example is an accounting illustration rather than a typical task quote.
Kimi Plans, Context Limits, and Usage Quotas
A million-token specification is not universal subscription entitlement. The Kimi Code model-configuration documentation says K3.1 Pro is available on Plus and higher plans, that a Pro-level plan is needed for the full 1M context in that product, and that Highspeed requires Pro or above. Some consumer pricing pages list different limits for Kimi's general app, so those plan grids should not be treated as interchangeable.
A user comparing subscriptions should verify the specific product surface: Kimi chat, Kimi Work, Kimi Code, or the metered developer API. Check maximum context, call quotas, high-speed eligibility, file-upload limits, model routing, and whether the advertised entitlement applies to a monthly or annual plan. The model's maximum context window is relevant only when the service actually permits it.
How to Use Kimi K3.1 Pro
Kimi's hosted access routes cover general chat, Kimi Work, Kimi Code, and the developer API. In Kimi Code, a user can choose the model from the interface or run /model in the CLI. The Kimi API platform exposes model identifiers such as kimi-k3.1-pro and kimi-k3.1-pro-highspeed; Kimi Code's own selector uses k3.1-pro and k3.1-pro-highspeed. Those names are not necessarily interchangeable across endpoints.
The Kimi Code model configuration guide recommends a fresh session when moving from an older model, because switching models or reasoning levels can invalidate context caches. It also says K3.1 Pro requires thinking mode and rejects requests that explicitly disable it. Supported effort choices include low, high, and max; specify an effort deliberately rather than assume that defaults match across every API and application.
A short trial should start with two or three representative jobs and record both outcomes and costs. For coding, require executable tests; for research, require source references; for 3D assets, require a valid export. Only after that should a team increase the context allowance, enable higher effort, or switch to Highspeed.
Is Kimi K3.1 Pro Open Source? Weights, License, and Safety
Kimi K3.1 Pro is currently a hosted model with an announced open-weight release. On October 27, 2026, Moonshot's stated plan is to publish the complete model weights by November 4. It is misleading to describe the weights as already downloadable or to promise a particular license before the repository and licensing documents appear.
Open weights and open source are not identical. Access to model weight files does not automatically provide training data, full training code, unrestricted redistribution, or permission for every commercial use. Even once weights become available, running a model with approximately 2.8 trillion total parameters is an infrastructure project, not a typical personal-laptop installation. Hosting costs, quantization, memory capacity, and serving software all need separate evaluation.
Why Moonshot Reduced Cyber Capabilities
Moonshot says it deliberately removed cyber-related material from mid-training data and reinforcement-learning environments for the planned open-weight checkpoint. On the company's internal xdev-bench-hard evaluation, the filtered model scored 81.0% versus 90.5% for a checkpoint without those precautions. This is a vendor-controlled comparison, not independent proof of safe or unsafe real-world behavior.

The policy choice illustrates a genuine tension: stronger coding agents can assist defenders with bug fixing, but software-exploitation capabilities can also be misused. Reuters' October 24 reporting described the mitigation steps and noted that the benchmark results had not been independently verified. Openly distributing weights also reduces the original publisher's ability to enforce later restrictions on copies that users control.
For enterprise adopters, safety due diligence should extend beyond the model's stated intent. Verify data-retention terms, deployment location, access permissions, logging, intellectual-property obligations, and whether a hosted API's controls carry over to a future self-hosted deployment. Open weights may improve inspection and autonomy, but do not eliminate the need for application-level security.
Should You Use Kimi K3.1 Pro?
Kimi K3.1 Pro deserves consideration for difficult coding, tool-driven research, and structured production tasks that can be checked by tests or reviewers. The independent agent benchmarks justify a trial; the model's slower-than-median output rate and relatively verbose reasoning argue against adopting it on score alone.
|
User or team |
Practical recommendation |
Main limitation to verify |
|---|---|---|
|
Software engineers |
Pilot on regression fixes and multi-file changes |
Test passes, elapsed time, retries |
|
3D artists and CAD teams |
Test script-assisted prototyping and exports |
Geometry validity and manufacturability |
|
Analysts and researchers |
Try document-grounded extraction with citations |
Source traceability and numerical accuracy |
|
High-volume chatbot builders |
Compare total task costs before migrating |
Output tokens and perceived latency |
|
Local-model developers |
Revisit after weights and license are published |
Hosting infrastructure and license terms |
The most revealing comparison is between a model's raw capabilities and the product someone expects to use. A personal assistant must also remember context, connect to authorized services, and complete actions reliably; the broader personal AI assistants guide explains those application-level requirements. K3.1 Pro may be the intelligence component in such a system, but a benchmark cannot tell whether the finished assistant works well.
Verdict: K3.1 Pro is a credible high-end reasoning model whose clearest independent gains are in agentic execution. It is not demonstrably the best option for every prompt, the full 1M context is not guaranteed by every subscription, and its open-weight status remains prospective until the files and license are published. For teams with measurable agent workflows, a limited production-like pilot is more informative than a leaderboard rank.
Frequently Asked Questions
Is Kimi K3.1 Pro free to use?
Limited access may be available through Kimi's consumer products, depending on plan and region, but that should not be confused with an unlimited free API. Kimi Code gives K3.1 Pro and Highspeed access according to specific membership tiers. Metered API requests have token charges even when the underlying model is also available inside a subscription service.
Does every Kimi plan include the full 1M-token context?
No. The underlying model supports up to 1,048,576 tokens, but product-specific entitlements differ. Kimi Code's October 2026 documentation reserves the full context for higher tiers; general consumer plan descriptions may use different eligibility rules. Check the currently selected app and plan rather than extrapolate from the model's technical ceiling.
Can Kimi K3.1 Pro run locally?
The full K3.1 Pro weights are not yet published as of October 27, 2026. Moonshot says it intends to release them by November 4. Local use, licensing, quantization, and practical hardware requirements should be reassessed when the actual release appears; a hosted API does not count as local inference.
Is Kimi K3.1 Pro better than Claude Opus 5.5?
Neither model wins every workload. K3.1 Pro has competitive independent agentic-coding results and a lower first-party token tariff than several frontier services, while Claude Opus 5.5 leads on some broader reasoning, knowledge, and other evaluated tasks. Compare the same tasks, harnesses, thinking effort, output quality, and billed cost before declaring an overall winner.
0 Kommentare