Usage limits
Kimi Code limits

Hit your Kimi Code usage limit?

Kimi Code plans apply a rolling five-hour rate window that recovers once it rolls over. Legacy plans also refresh a weekly quota every seven days from the subscription date, and every plan shares the membership's monthly total.

$curl -fsSL https://www.openllm.sh/install | bash
$openllm opencode

What you'll see

Moonshot states that once the monthly total is reached, Kimi Code quota is frozen until it resets or you upgrade.

Keep working through the wall

Launch your agent through OpenLLM and give its model alias a fallback chain. When your Kimi Code allowance is exhausted, that entry is cooled and the request continues on the next plan or API key you hold.

  • openllm opencode
  • openllm claude

Fallback chains when a model is rate-limited

Define an ordered chain per model alias. When a hop returns a rate limit, an overload or a provider error, the request moves to the next hop instead of failing your session.

  • Chains are configured once and shared by every client and device
  • Each hop resolves its own model settings, so a fallback never inherits the wrong parameters
  • Every hop that ran is visible in your request history

See where the tokens go

Requests, tokens, latency and API-equivalent cost per model and provider, with charts you can export or share.

Questions

Something else? Contact us

Checked 2026-09-25 against Kimi Code membership.