Coding plans

The Free plan's usage is labelled 'Limited' with no dollar or request amount. It includes Agent, Chat and Tab completions with Cursor models (Grok and Composer), per the Cursor models and pricing docs. The page does not list the exact models. usage is described only as 'Limited'; no dollars, requests or tokens are published for it.

Everyday Usage allows 10-50 prompts every 5 hours, including image and video uploads. At the limit you can upgrade to the next plan or wait for the limit to refresh. Subscriptions work only in the Muse Code CLI. the allowance is a prompt range (10-50 per 5 hours) with no published token or dollar conversion for subscriptions; API rates are published separately.

A fixed monthly quota of 4.1 billion credits, converted to tokens at the published per-model rates. When the quota runs out the service pauses; it does not draw on bonus or account balance. Unused quota does not carry over, and no 5-hour or weekly cap is listed.

A monthly quota of 11,500 credits; the weekly cap was removed on September 22, 2026. Credits per request depend on the model, token usage, thinking mode and tool calls, and the console shows per-call usage. 1-2 concurrent agents. Credits; Alibaba publishes no credit-to-token rate (the page says credits are dynamically determined by model type, token usage, thinking mode and tool calls).

The same plan in its other storefront.

Paid plans include a weekly pool of usage for Cursor models, shared across Grok and Cursor. Different models draw from the pool at different rates. The pool is described only as a multiple of Plus ('Base'); no dollar or request amount is published. Cursor publishes per-token rates for usage beyond the pool. pool sizes are published only as multiples of Plus ('Base', '4x Plus', '15x Plus', '50x Plus'), with no dollar or request conversion.

A monthly quota of 25,500 credits; the weekly cap was removed on September 22, 2026. Credits per request depend on the model, token usage, thinking mode and tool calls, and the console shows per-call usage. 2-3 concurrent agents. Credits; Alibaba publishes no credit-to-token rate.

The same plan in its other storefront.

Usage limits are defined as monthly dollar amounts, set per model. A model's 5-hour limit is 20% of its monthly limit, its weekly limit is 50% and its monthly limit is 100%. The FAQ says these quotas are enforced across rolling windows. Request counts shown per model are estimates.

Usage is metered in credits, not prompts: (input tokens x input multiplier + cached input tokens x cached multiplier + output tokens x output multiplier) / 10,000. GLM-5.3 multipliers are 6.9 input, 1.7 cached input and 24 output; GLM-5.3-Flash are 2.3, 0.56 and 8. Web Search, Web Reader and Zread MCP calls are charged as number of calls x 1.2. Models and MCP tools share one quota.

The same plan in its other storefront.

A fixed monthly quota of 11 billion credits, converted to tokens at the published per-model rates. When the quota runs out the service pauses; it does not draw on bonus or account balance. Unused quota does not carry over, and no 5-hour or weekly cap is listed.

High Usage is stated as 5x the Everyday Usage allowance, with more multimodal inputs. No separate prompt count is given for this tier. Subscriptions work only in the Muse Code CLI. the allowance is a multiple of the Everyday prompt range, with no published token or dollar conversion.

Plus and higher plans have a rolling 5-hour usage limit and no weekly limit, plus a monthly shared credit pool. The official pages give no numeric values. Once the monthly pool is used up, Kimi Code is frozen until it resets or the plan is upgraded. Unused credits do not roll over. Credits and usage limits with no published number or conversion to tokens or dollars.

A monthly quota of 45,000 credits; the weekly cap was removed on September 22, 2026. Credits per request depend on the model, token usage, thinking mode and tool calls, and the console shows per-call usage. 3-4 concurrent agents. Credits; Alibaba publishes no credit-to-token rate.

The same plan in its other storefront.

Usage is measured relative to Go: Go is 1x (baseline), Explore is 3x and Build is 7.5x. Each tier has a 5-hour window and a weekly window; when a window ends, usage resets to the tier's full limit. Actual consumption varies with model, context length and task complexity. No token or dollar figures are published. Only relative multiples of Go are published; no conversion to tokens or dollars.

Paid plans include a weekly pool of usage for Cursor models, shared across Grok and Cursor. Premium is stated as '4x more usage compared to Plus'; no dollar or request amount is published. Third-party models are not in the pool: they are billed at the model's API list price from prepaid credit. Cursor publishes per-token rates for Cursor models beyond the pool. the pool is stated only as '4x Plus', with no dollar or request conversion; third-party usage is billed at published API list prices.

Plus and higher plans have a rolling 5-hour usage limit and no weekly limit, plus a monthly shared credit pool. The official pages give no numeric values. Once the monthly pool is used up, Kimi Code is frozen until it resets or the plan is upgraded. Unused credits do not roll over. Credits and usage limits with no published number or conversion to tokens or dollars.

Usage limits are defined as monthly dollar amounts, set per model. A model's 5-hour limit is 20% of its monthly limit, its weekly limit is 50% and its monthly limit is 100%. The page describes Go Plus as 'Higher limits and fewer interruptions'. The FAQ says these quotas are enforced across rolling windows.

A fixed monthly quota of 38 billion credits, converted to tokens at the published per-model rates. When the quota runs out the service pauses; it does not draw on bonus or account balance. Unused quota does not carry over, and no 5-hour or weekly cap is listed.

Power Usage is stated as 20x the Everyday Usage allowance, with access to the most powerful Muse models, including Muse Wonder Full, early feature access and higher file uploads. No separate prompt count is given for this tier. Subscriptions work only in the Muse Code CLI. the allowance is a multiple of the Everyday prompt range, with no published token or dollar conversion.

Usage is measured relative to Go: Go is 1x, Explore is 3x and Build is 7.5x. Each tier has a 5-hour window and a weekly window; when a window ends, usage resets to the tier's full limit. Actual consumption varies with model, context length and task complexity. No token or dollar figures are published. Only relative multiples of Go are published; no conversion to tokens or dollars.

Usage is metered in credits, not prompts: (input tokens x input multiplier + cached input tokens x cached multiplier + output tokens x output multiplier) / 10,000. GLM-5.3 multipliers are 6.9 input, 1.7 cached input and 24 output; GLM-5.3-Flash are 2.3, 0.56 and 8. Models and MCP tools share one quota.

The same plan in its other storefront.

A monthly quota of 180,000 credits; the weekly cap was removed on September 22, 2026. Credits per request depend on the model, token usage, thinking mode and tool calls, and the console shows per-call usage. 6-8 concurrent agents. Credits; Alibaba publishes no credit-to-token rate.

The same plan in its other storefront.

Plus and higher plans have a rolling 5-hour usage limit and no weekly limit, plus a monthly shared credit pool. The official pages give no numeric values. Once the monthly pool is used up, Kimi Code is frozen until it resets or the plan is upgraded. Unused credits do not roll over. Credits and usage limits with no published number or conversion to tokens or dollars.

Paid plans include a weekly pool of usage for Cursor models, shared across Grok and Cursor. Super is stated as '15x more usage compared to Plus' and adds priority model access at peak times over Premium; no dollar or request amount is published. Third-party models are billed separately at API list price from prepaid credit. the pool is stated only as '15x Plus', with no dollar or request conversion.

A fixed monthly quota of 82 billion credits, converted to tokens at the published per-model rates. When the quota runs out the service pauses; it does not draw on bonus or account balance. Unused quota does not carry over, and no 5-hour or weekly cap is listed.

Usage is metered in credits, not prompts: (input tokens x input multiplier + cached input tokens x cached multiplier + output tokens x output multiplier) / 10,000. GLM-5.3 multipliers are 6.9 input, 1.7 cached input and 24 output; GLM-5.3-Flash are 2.3, 0.56 and 8. Models and MCP tools share one quota.

The same plan in its other storefront.

Usage is measured relative to Go: Go is 1x, Explore is 3x and Build is 7.5x. Each tier has a 5-hour window and a weekly window; when a window ends, usage resets to the tier's full limit. Actual consumption varies with model, context length and task complexity. No token or dollar figures are published. Only relative multiples of Go are published; no conversion to tokens or dollars.

Plus and higher plans have a rolling 5-hour usage limit and no weekly limit, plus a monthly shared credit pool. The official pages give no numeric values. Once the monthly pool is used up, Kimi Code is frozen until it resets or the plan is upgraded. Unused credits do not roll over. Credits and usage limits with no published number or conversion to tokens or dollars.

Paid plans include a weekly pool of usage for Cursor models, shared across Grok and Cursor. Ultra is stated as '50x more usage compared to Plus' and adds earliest access to all products and models over Super; no dollar or request amount is published. Third-party models are billed separately at API list price from prepaid credit. the pool is stated only as '50x Plus', with no dollar or request conversion.

Maximum Usage is stated as 80x the Everyday Usage allowance, with everything in Power Usage. No separate prompt count is given for this tier. At the limit there is no higher tier, so the subscriber must wait for the limit to refresh. Subscriptions work only in the Muse Code CLI. the allowance is a multiple of the Everyday prompt range, with no published token or dollar conversion.

A monthly quota of credits; the weekly cap was removed on September 22, 2026, and no 5-hour limit is listed. Credits per request depend on the model, token usage, thinking mode and tool calls, and the console shows per-call usage. Lite allows 1-2 concurrent agents. Credits; Alibaba publishes no credit-to-token rate (the page says credits are dynamically determined by model type, token usage, thinking mode and tool calls).

A monthly quota of credits; the weekly cap was removed on September 22, 2026, and no 5-hour limit is listed. Credits per request depend on the model, token usage, thinking mode and tool calls. Essential allows 2-3 concurrent agents. Credits; Alibaba publishes no credit-to-token rate.

Usage is metered in credits, not prompts: (input tokens x input multiplier + cached input tokens x cached multiplier + output tokens x output multiplier) / 10,000. GLM-5.3 multipliers are 6.9 input, 1.7 cached input and 24 output; GLM-5.3-Flash are 2.3, 0.56 and 8. Models and MCP tools share one quota.

The same plan in its other storefront.

A monthly quota of credits; the weekly cap was removed on September 22, 2026, and no 5-hour limit is listed. Credits per request depend on the model, token usage, thinking mode and tool calls. Standard allows 3-4 concurrent agents and includes Harness benefits (metered separately). Credits; Alibaba publishes no credit-to-token rate.

Usage is metered in credits, not prompts: (input tokens x input multiplier + cached input tokens x cached multiplier + output tokens x output multiplier) / 10,000. GLM-5.3 multipliers are 6.9 input, 1.7 cached input and 24 output; GLM-5.3-Flash are 2.3, 0.56 and 8. Models and MCP tools share one quota.

The same plan in its other storefront.

A monthly quota of credits; the weekly cap was removed on September 22, 2026, and no 5-hour limit is listed. Credits per request depend on the model, token usage, thinking mode and tool calls. Pro allows 6-8 concurrent agents. Credits; Alibaba publishes no credit-to-token rate.

Usage is metered in credits, not prompts: (input tokens x input multiplier + cached input tokens x cached multiplier + output tokens x output multiplier) / 10,000. GLM-5.3 multipliers are 6.9 input, 1.7 cached input and 24 output; GLM-5.3-Flash are 2.3, 0.56 and 8. Models and MCP tools share one quota.

The same plan in its other storefront.