All coding subscriptionsChina price
Kimi Allegro
Moonshotmax$103
listed at CNY 699
Last checked: 2026-07-29
- First limit you hit
- Only a ratio to another plan
- Equivalent API value
- —
- Value multiple
- —
- When it runs out
- 加油包 (Extra Usage) top-up, priced per pack
- Scenario
- Interactive use only
Allowances
60× Kimi Andante
x the Andante tier's Kimi Code allowance
›The vendor's own wording
"Kimi Code 60 倍额度", quoted against the same unpublished baseline.Open the source page
Vendor publishes no figure
rolling 5-hour rate window, figure not published
›The vendor's own wording
"除了周额度外，还有每 5 小时的滚动频率窗口——即使总量充足，短时间请求过多也会 触发限流，等窗口滚动后自动恢复。" The pricing page defers the number to the product surface: "5小时及周频控请以页面提示为准。"Open the source page
Models included
| Model | Capability | Burn rate | |
|---|---|---|---|
| kimi-for-coding (Kimi K2.7 Code)default | untiered | 1 | |
| k3 (Kimi K3, up to 1M) | untiered | 1 | "Allegretto 及更高档位支持最高 1M 上下文." |
| k3-256k (Kimi K3, 256K) | untiered | 1 | |
| kimi-for-coding-highspeed (K2.7 Code HighSpeed) | untiered | 3 | "Allegretto 档位以上". Kimi prices the speed explicitly: "高速版（6 倍速 3 倍消耗）" — same coding ability, about 5-6x the output speed, 3x the quota consumption. |
Subscription versus your own API key
This compares two ways of working the same way — in an IDE or CLI, where BYOK tools make a direct API key a real option. It is not a claim that subscriptions are cheaper than the API in general.
| Model | Effective price / 1M tokens | vs API rate | Breakeven |
|---|---|---|---|
| kimi-for-coding (Kimi K2.7 Code)untiered | — | — | 126.2M |
| k3 (Kimi K3, up to 1M)untiered | — | — | 39.5M |
| kimi-for-coding-highspeed (K2.7 Code HighSpeed)untiered | — | — | 63.1M |
Usage terms
Quoted from the vendor's own terms. We do not give legal advice.
Kimi names the tools the benefit covers — Kimi Code CLI, Claude Code and Roo Code — and warns against the rest: "在其他未列出的平台或工具中使用 Kimi Code 的 API Key，可能会被视为滥用行为，并可能导致权益受限。" The benefit is also scoped to individuals: "请注意，本权益仅用于个人开发，非用于企业开发场景。" Client identification may not be faked: "篡改客户端标识（User-Agent）将被视为 违规".
Change history
- 2026-07-29Recorded from the seed file
- 2026-07-28Recorded from the seed file
- 2026-07-28Recorded from the seed file