Yesteraday you updated limits (500 requests before / percentage now). problem is that now i cant use my $40 subsctiption cause of 429 error….
I guess you have trouble with rate limit logic… or UI shows incorrect percentage.
LLM provider error: Error code: 429 - {‘error’: {‘message’: “We’re receiving too many requests at the moment. Please wait a moment and try again.”, ‘type’: ‘rate_limit_reached_error’}}
Thanks for flagging this — I understand the frustration of hitting a 429 error right after the billing model change.
From what I understand, this relates to a recent update on the Kimi Code side (Membership Benefits logic), where they shifted from request-count-based packages to token-based packages. The intention behind this change is actually to provide better value for users, particularly in scenarios where context caching is involved, as you can get significantly more usage out of the same spend versus the old request-based model.
However, you’re right that the error messaging here is problematic. The generic 429 response ("We're receiving too many requests...") appears to be conflating different types of limits. In your case, this is likely hitting a concurrency limit rather than the token quota being exhausted — the error type distinction isn’t being surfaced properly in the current implementation.
The Kimi Code team is aware of the confusion and has committed to updating the documentation at Kimi Code Membership Benefits | Kimi Code Docs to clarify the new token-based billing strategy and the specific rate limiting behaviors (including concurrency vs. quota limits). I’d recommend keeping an eye on that page for the elaborated policy docs, which should go live shortly.
Just to add a bit of context: that limit is essentially a safety brake to prevent accidental spikes from exhausting your token package prematurely. It’s not meant to throttle your work, and I know the team is already evaluating usage patterns to set a more reasonable threshold.
