Is this about Kimi Code’s API running out of quota?
Thanks for your support! The $99/month Allegro plan should generally be quite durable for any individual user, so if you’re pushing its limits within just a few days, we truly appreciate you being such a power user!
Regarding the “out of quota” message, there are two different limits to check:
1. Throughput Capacity (5-hour rolling window)
If you’re seeing intermittent 429 errors that come and go, you’re likely hitting the throughput limit rather than your weekly cap. Kimi Code operates on a 5-hour time window that releases tokens for each user to prevent abusive burst traffic. As noted in our docs (https://www.kimi.com/code/docs/en/#key-advantages):
Throughput Capacity: A 5-hour token quota supports approximately 300–1,200 API calls, with a maximum concurrency of 30, ensuring uninterrupted operation for complex workloads.
I previously shared some tips in this forum thread about using the usage API (https://api.kimi.com/coding/v1/usages) to adaptively check your quota programmatically.
2. Weekly Quota
If you’re completely blocked with a hard “quota exceeded” message, you’ve likely consumed your weekly allowance (which resets every 7 days). Please check your Dashboard:
- Look at the Weekly usage indicator at the very top. If this shows 100% consumption after just 3 days of intensive use, you’re definitely a power user and we appreciate your heavy usage!
- Please also review the Usage History section at the bottom. Check if the timestamps and request volumes match your actual usage pattern. If you see suspicious activity (e.g., requests when you weren’t using the API, or unusually high token counts), this could indicate an API key leak. Please verify your API keys haven’t been compromised if the consumption pattern seems unusual.
Let us know what the Weekly usage meter and Usage History show (please mask the request id), and we may help investigate further!