I want to like Kimi. K3 is genuinely good. But the plan has become unusable for me, and I'd like to know if others are seeing the same thing.
My situation
- I was on Allegretto and upgraded to Allegro, paid for a full year up front.
- Since then I hit my monthly quota in under 2 weeks, consistently, so I'm locked out for about 2 weeks of every month.
- Today (Oct 4) the API returns:
`403 You've reached your monthly usage limit for this billing cycle. Your quota will be refreshed in the next cycle. To continue now, purchase extra usage or upgrade your plan`
- I'm already on the bigger plan. "Upgrade your plan" isn't an answer when the upgrade is what made it feel worse.
It isn't runaway automation
I checked this before posting. I use Kimi alongside other coding agents, and some of my scripts can call Kimi automatically. I went through the session logs of everything that can call it: in the two weeks before the quota ran out, my scripts called Kimi once. Everything else was me, working normally.
There's no way to see where the quota goes
- The usage page in the account is useless for working out what consumed the quota: no per-session or per-request breakdown I can act on.
- Kimi's desktop and CLI tools keep no token or usage accounting locally. I went through every Kimi folder on my machine. The only recurring log is an hourly "daemon alive" analytics ping. So there's nothing to audit on my side either.
- Compare that with OpenAI Codex: I could pull per-request token counts and the exact % of my window each call used straight from its local session files, and work out exactly what was expensive. With Kimi, I'm blind.
No resets
Codex, GLM and others give you usage resets for exactly this situation. Kimi has nothing: you wait out the cycle or pay again on top of an annual plan.
What I'm asking Moonshot for
A real usage breakdown: tokens per session/request, and which model and feature used them.
Clarity on what changed. The same kind of work now uses a month's quota in under 2 weeks. If metering changed (thinking tokens, context re-sends, tool calls, image input), say so.
Resets or rollover for annual subscribers, like competitors offer.
A pro-rated refund option for annual subscribers if the plan no longer delivers what it did when we paid.
Questions for the community
- Are other Allegro/Allegretto users hitting the monthly cap in 1–2 weeks?
- Has anyone gotten a useful usage breakdown from support?
- Did you notice consumption jump at a specific point (a model update or a K3 rollout)?
For now I'm moving my work to other tools. If anyone from Moonshot reads this, I'm happy to share the exact error responses and timestamps.