
Kimi
Moonshot AI's assistant and agent, built on its own Kimi modelsReference profile
About Kimi
Kimi is Moonshot AI's chat and agent product for individuals and businesses. People use the web, app and desktop clients (kimi.com in China, kimi.ai internationally) plus agents such as Kimi Code, Kimi Work, and Kimi Claw; developers call the same model family through platform.kimi.com (CNY, api.moonshot.cn) or platform.kimi.ai (USD). The hosted product and APIs are closed-source commercial services. Separately, Moonshot publishes Kimi K3 model weights under the Kimi K3 License; weights for the flagship Kimi K3.1 Pro are promised by 2026-11-04 and were not on Hugging Face as of 2026-10-25.

What problem it solves
Kimi sets out to let people do research, writing, coding and multi-step tasks in natural language: users chat or start an Agent in the consumer clients, and developers wire the same models into their own products through the API. The company's official about page says Moonshot AI was formally founded in spring 2023.
Product surface (2026-10-25). Consumer domains are split between kimi.com in China and kimi.ai internationally; the open platform is likewise split into two consoles with separate billing, China (platform.kimi.com, whose inference docs point to api.moonshot.cn) and international (platform.kimi.ai). The current main chat models listed in the open platform's "models" doc include kimi-k3.1-pro (flagship; the vendor states about 3T total parameters, 1M context and vision support), kimi-k3.1-pro-highspeed (the vendor says same capabilities, aimed at higher throughput), kimi-k3 (previous flagship: 2.8T total parameters, about 104B activated, a 1,048,576-token context, native vision, weights released), and coding-oriented kimi-k2.7-code / kimi-k2.7-code-highspeed plus general-purpose kimi-k2.6. The notice on the models and pricing pages says the K2 series is closed to newly registered users from 2026-10-31 (existing users unaffected) and that all K2-series models are planned to retire at the end of December; kimi-k2.7-code / kimi-k2.7-code-highspeed / kimi-k2.6 above all belong to the K2 series and are in scope. When migrating, switch to the replacement model names the docs give rather than keep writing old IDs into long-lived configs.
K3.1 Pro and open weights. The "Kimi K3.1 Pro quickstart" says the weights will be released "by November 4". On 2026-10-25 the released Kimi-K3 was available under the moonshotai namespace on Hugging Face (with LICENSE and README at the root); Kimi-K3.1-Pro weights had not yet been released as of 2026-10-25. The Kimi-K3 README states 2.8T total parameters, 104B activated, a 1,048,576-token context, and text plus image modality (native vision), and points to the Kimi K3 License. In other words, the fact that kimi-k3.1-pro can already be called through the API doesn't mean its weights are publicly downloadable.
Billing has to be read separately. Membership subscriptions (Go / Plus / Pro / Max / Ultra and so on) buy consumer-side quota and features, refreshed monthly with no rollover; the open-platform API debits an account balance per token, priced in CNY in China and in USD internationally. They are not the same bill, and Agent quota in a membership can't be treated as API balance. The model service agreement (the docs page shows an update date of 2026-08-31) governs API callers; consumer use is separately covered by the kimi.com / kimi.ai user agreement and privacy policy.
Seek the optimal way to turn energy into intelligence
Core capabilities
Flagship and Highspeed tiers. The open platform sells K3.1 Pro as Standard and Highspeed: the capability description is the same, Highspeed targets higher concurrency and lower latency, and its unit price is about twice Standard's. For caching, the homepage lists write and hit prices separately; hits are much cheaper than writes (CN hit ¥1.30 / M tokens, international hit $0.20 / M tokens, as of 2026-10-25). The homepage lists only one write price with no TTL; the pricing page and context-caching docs say K3-series cache writes are billed separately by TTL, 5 minutes (default) or 1 hour, with the 1-hour tier priced higher. For kimi-k3 (per M tokens): CN input (miss) ¥20, write 5m ¥20 / 1h ¥40, hit ¥2; international $3, write 5m $3 / 1h $6, hit $0.30. K3.1 Pro supports about 1M context and vision input; parameter counts, benchmarks and capability statements are all vendor claims.
Open weights ≠ open product. Kimi-K3 on Hugging Face can be downloaded under the Kimi K3 License for self-run inference; the consumer apps, web, Kimi Code / Work / Claw and the hosted API remain closed commercial services. The license grants MIT-style rights (use, copy, modify, distribute, sublicense and sell) with several added conditions (the original text governs): section 1, keep the copyright and license notices; section 2, if the licensee or an affiliate runs a MaaS business and the licensee together with its affiliates has total revenue above USD 20M in any consecutive 12 months, a separate agreement with Moonshot is required before any commercial use (the license defines MaaS as an inference or fine-tuning service that lets third parties substantially control inputs, parameters or training data; features merely embedded in an end product, or simply relaying requests to models hosted by others, don't count); section 3, use in a commercial product with more than 100M monthly active users or more than USD 20M monthly revenue requires prominently displaying "Kimi K3" in the user interface; section 4, internal use (not providing the software, its outputs or capabilities to third parties), and use through Moonshot's official products or certified inference partners, are exempt from sections 2 and 3.
Agent and coding line. The membership help center describes the tiers: Go covers documents, slides, deep research and website deployment, without Kimi Code; Plus and up add Kimi Code and Agent clusters; Pro and up emphasise goal mode and a dedicated Kimi Claw; Max / Ultra raise the limits on parallelism, scheduled tasks and project storage (the help center's Ultra example: about 28× Agent quota, 4 parallel tasks, 25 each of scheduled and widget tasks; the purchase page governs). Kimi Code also has a rolling 5-hour usage cap (new plans have no weekly cap; legacy plans such as Andante keep it). The help center also says a deployed Claw cloud host, even with no active task, deducts a sandbox fee of about 0.6% of membership quota per day (settled at 4 p.m. daily), and a website published by an Agent costs about 0.08% for hosting. Charges stop only once the files are saved and the cloud host deleted, or the site unpublished.
Enterprise options. The open-platform docs say the Kimi API open platform is pay-as-you-go with no subscription plans, unlike Kimi membership, Kimi Code and other products. "No subscription plans" refers only to how the API open platform bills, not to Kimi membership or Kimi Code subscriptions; the open-platform docs navigation also has "Enterprise subscription" and "Contact sales" entries, plus a Zero Data Retention (ZDR) page for customers with requirements on inference log retention. Eligibility, covered models and contract text are as set in the console and commercial terms.
How it compares
Versus buying only the API. Membership suits individuals or small teams who want Agent, Code and Claw inside the official clients; the API suits embedding the models in your own product, metered by token. Membership quota and API balance don't transfer between each other (per the help center and the open-platform account docs). If the work is mainly backend calls, maxing out Ultra isn't necessarily a better fit than pay-as-you-go API; conversely, if you rely heavily on the official Agent products, topping up only the API won't get you Code / Claw rights in the clients.
Versus downloading only the open weights. Self-hosting Kimi-K3 avoids per-token fees, but you supply the inference hardware, troubleshooting and upgrades yourself, and must follow the Kimi K3 License's MaaS and attribution terms; the official hosted API and consumer products are outside that license's "freely redistributable software" scope. The K3 weights themselves support vision and 1M context; the difference is that K3.1 Pro is the newer flagship, for now callable only through the official API, with weights not yet released.
China site versus international site. Domains, currencies and plan tiers aren't symmetric: China membership has Go (from ¥49/month), while the current tiers listed in the international help center run from Plus (from $19/month) to Ultra, with no tier equivalent to China's Go. The API is likewise split between platform.kimi.com (CNY) and platform.kimi.ai (USD). Unit prices for the same model name on the two sides can't be compared for "which is cheaper" just by converting at the exchange rate, because the billing entity, taxes and regional terms differ, and the cache price fields shown on the homepages shouldn't be mixed either.
Versus similar general assistants. Kimi sells consumer subscriptions and a developer API at the same time, and separately releases K3 weights; that structure differs from vendors that do only an API, only a chat app, or only open weights.
Who it's for / Not for
Who it's for
Individual users who need long documents, research and writing in Chinese and want to use Agent / website deployment directly in the official clients (China Go and up, per the help-center tier descriptions).
Developers and heavy users who need Kimi Code, more parallelism or Claw cloud hosts (China Plus and up; international Plus and up).
Teams that want to connect kimi-k3.1-pro and other models to their own products and pay per token (China or international open platform).
Teams that can build their own inference and accept the Kimi K3 License's commercial limits: they can download the Kimi-K3 weights for local or private deployment.
Who it's not for
Teams that require the consumer clients or hosted API to be "fully open-source, auditable and re-licensable": the products and API are closed commercial services.
People who can't accept a shared membership quota pool, daily charges for Claw cloud hosts, or Code's rolling 5-hour cap: these rules are in the membership help center, and running out affects other features.
Teams that run a MaaS business whose total revenue together with affiliates may exceed USD 20M in any consecutive 12 months, yet plan to use Kimi-K3 commercially without first signing a separate agreement with Moonshot: section 2 of the license requires signing before commercial use.
Projects that need to rely on K2-series models long-term: the vendor has published the K2 retirement timetable (closed to newly registered users from 2026-10-31, with all K2-series models, including kimi-k2.7-code / kimi-k2.6, planned to retire at the end of December).
People who need "already published" K3.1 Pro open weights: as of 2026-10-25 the vendor says the weights will be released by 2026-11-04, and the public repo is not up yet.
Getting started
Consumer. Open kimi.com (China) or kimi.ai (international); after signing up you can try basic chat, and paid tiers are bought from the "Subscription / Membership" entry in the client. The help-center tables carry screenshots dated 2026-10-19; the purchase page on the day of ordering governs. Users on legacy China plans can keep tiers such as Andante or upgrade via the options on the page; the international help center doesn't describe the same legacy plan naming as China.
Open platform. China: sign up at platform.kimi.com, create an API key, and call per the "models" and "quickstart" docs (the docs give the inference domain as api.moonshot.cn). International: platform.kimi.ai. Use the model IDs listed in the docs (for example kimi-k3.1-pro); K2-series IDs have been announced for retirement. The K3.1 Pro quickstart also states some top-up thresholds and voucher exclusion rules, so a test account may be unable to call the flagship model because of voucher rules.
Self-hosted weights. Download from Hugging Face moonshotai/Kimi-K3; LICENSE and README are at the root, and deployment uses your own inference stack. The license has specific commercial-use terms covering where the attribution text goes and the threshold for a written MaaS agreement. K3.1 Pro can currently be called only through the API; its weights have not been released.
Enterprise and ZDR. The open platform has a "Contact sales" entry for explaining data-retention and regional needs; whether ZDR covers the target models, the scope of logs and the audit method need to be confirmed in writing.
Pricing & license
Prices as of 2026-10-25. Membership tables come from the help centers (screenshots dated 2026-10-19); API unit prices come from the public prices on the open-platform homepages. Prices may change by the day of ordering.
China membership (kimi.com, CNY). Monthly auto-renew / annual auto-renew total: Go ¥49 / ¥468; Plus ¥99 / ¥948; Pro ¥199 / ¥1,908; Max ¥699 / ¥6,708; Ultra ¥1,399 / ¥13,428. Annual billing charges the full year's total at once. Go excludes Kimi Code; Plus and up include it. Legacy plans (Andante and others) can be kept; the rules are in the help center.
International membership (kimi.ai, USD). Plus $19 / $180; Pro $39 / $372; Max $99 / $948; Ultra $199 / $1,908 (monthly / annual total). The current plans listed in the international help center start at Plus.
China API (platform.kimi.com, CNY / M tokens). Homepage: kimi-k3.1-pro input ¥13, output ¥68, cache write ¥13, hit ¥1.30; kimi-k3.1-pro-highspeed input ¥26, output ¥136, write ¥26, hit ¥1.30. The homepage write price has no TTL label; the caching doc says the default TTL is 5 minutes, with a 1-hour tier at a higher unit price. kimi-k3: the official context-caching doc example gives input (miss) ¥20, cache write 5m ¥20 / 1h ¥40, hit ¥2.
International API (platform.kimi.ai, USD / M tokens). Homepage: kimi-k3.1-pro $2 / $10, cache write $2, hit $0.20; Highspeed $4 / $20, write $4, hit $0.20; kimi-k3 $3 / $15, write $3, hit $0.30. The homepage write price likewise has no TTL label; the international caching doc, using kimi-k3 as the example, gives 5m write $3 and 1h write $6.
License. Consumer clients and API: closed commercial, governed by the user agreement and the model service agreement. Open weights: Kimi-K3 uses the Kimi K3 License (see the LICENSE on Hugging Face); K3.1 Pro weights had not yet been released as of 2026-10-25.
Risks & limits
Two billing systems, two regions. Mainland and international accounts differ in currency and plans. The same model is priced separately on each side: kimi-k3.1-pro is ¥13 input / ¥68 output on the mainland and $2 input / $10 output internationally; kimi-k3 is ¥20 input (cache miss) on the mainland and $3 input / $15 output internationally (all per million tokens, as of 2026-10-25). Membership quota is not API credit. Cross-border teams therefore face the question of which side holds the primary account, and which contracting entity issues invoices and handles compliance.
Quota and extra deductions. Membership features draw on one shared monthly pool, so running it down affects several features at once. Kimi Code adds its own rolling 5-hour cap, and Claw cloud hosts and published sites deduct a daily percentage of quota until they are deleted or unpublished (the help center lists the rates). Quota details can lag briefly; the help center says the balance currently shown is the one that counts.
Model lifecycle. The K2 series is being retired: closed to new sign-ups from October 31, 2026, with shutdown planned for the end of December 2026. Integrations that call old model names will need to migrate. The K3.1 Pro open-weights date is an announcement, not a delivery; plan around the weights actually appearing in the repo.
Licence and terms. Serving Kimi-K3 weights to outside users falls under section 2 (the MaaS aggregate-revenue threshold), section 3 (UI attribution) and section 4 (exemptions); the user carries the risk of a breach. The model service agreement and the user agreement set their own rules on prohibited uses, account security and data, and their original text governs. Teams that feed model output into automated decisions still need their own compliance review; the vendor's agreements don't replace it.
Capability claims. Parameter counts, context lengths and benchmark scores come from official docs or model cards. They are vendor-reported and vendor-tested.
Our verdict
Kimi runs consumer subscriptions, a developer API and open weights for some models side by side: membership in the official clients suits individuals who want convenience, the region-split open platform suits embedding in products, and the Kimi-K3 open weights suit private deployments by teams able to carry inference and license compliance themselves. The billing entity, the region, and choices about Highspeed or Claw all change the monthly cost structure significantly. The K2 retirement and the K3.1 Pro weight-delivery timetable mean old model names won't stay available for long, and the schedule for engineering integrations depends on the official migration notes.
Why it matters
Kimi is Moonshot AI's assistant, known for long context and the open-weight Kimi K2 models.
Sources
Official
- Context Caching (in Chinese) · Accessed Oct 25, 2026
- Kimi Membership Pricing (in Chinese) · Accessed Oct 25, 2026
- Kimi User Service Agreement (in Chinese) · Accessed Oct 25, 2026
- Kimi Privacy Policy (in Chinese) · Accessed Oct 25, 2026
- Kimi · Accessed Oct 25, 2026
- Membership Benefits | Kimi Code Docs · Accessed Oct 25, 2026
- Zero Data Retention · Accessed Oct 25, 2026
Media & third party
- Moonshot AI · Accessed Oct 25, 2026
- Membership Plans and Pricing · Accessed Oct 25, 2026
- moonshotai/Kimi-K3 · Hugging Face · Accessed Oct 25, 2026
- LICENSE · moonshotai/Kimi-K3 · Accessed Oct 25, 2026
- README.md · moonshotai/Kimi-K3 · Accessed Oct 25, 2026
Related products
- Kimi API Platform · Accessed Oct 25, 2026
- Kimi Open Platform · Accessed Oct 25, 2026
- Model List - Kimi API Platform · Accessed Oct 25, 2026
- Kimi K3.1 Pro - Kimi API Platform · Accessed Oct 25, 2026
- Model Inference Pricing Explanation - Kimi API Platform · Accessed Oct 25, 2026
- Context Caching · Kimi API Platform · Accessed Oct 25, 2026
- Terms of Service for Kimi OpenPlatform - Kimi API Platform · Accessed Oct 25, 2026
- Kimi · Accessed Oct 25, 2026
Updates & reading
A Tougher AI Leaderboard Leaves More Than Open-Weight Models Behind
Artificial Analysis says its Intelligence Index v5 widened the gap between open-weight models and the leader to 12 points from 3, and critics say a test that is 60% private can't be checked. The firm's own per-test scores show that many closed models fell alongside open-weight ones on the new tests, and that more than half of DeepSeek's deficit to the top models comes from public benchmarks anyone can rerun.
Vals AI says Kimi K3.1 Pro ranks #1 among open-weight models on its Vals Science Index
4 posts on XBefore Kimi's Quota Apology, Its Coding Agent Handed the Call on Helper Agents Back to Users
Moonshot adjusted parameters to reduce unnecessary subagent calls, Reuters reported. Public pull requests show its coding agent could spawn subagents, even a swarm of up to 128, without being asked. Now that takes an explicit request or a user switch.
Moonshot apologizes for Kimi K3.1 Pro rate limits, resets 25% of every subscriber's monthly quota
Moonshot AI's Kimi apologized on Oct 26 for rate limiting and unnecessary quota use on its K3.1 Pro subscription plan, calling the issues its own. Every active subscriber gets a one-time reset restoring 25% of the monthly quota (about a week of use); usage below 25% resets to zero. Kimi also says it is cutting unnecessary sub-agent calls and output length.
3 sources · 1 post on XKimi Code 2.3.2 makes single-agent the default; subagents and Agent Swarm now need explicit opt-in
Kimi Code CLI 2.3.2 changes its defaults: the agent now handles tasks itself instead of proactively spawning subagents, and delegation must be requested in the prompt, AGENTS.md, a skill or a multi-agent mode. The agent can no longer launch AgentSwarm on its own; swarms run only when the user turns on swarm mode, so they are unavailable in headless kimi -p runs and ACP clients such as Zed.
2 sources