Add a second account. kRouter rotates across accounts automatically, so the work continues on the next one the moment this one is exhausted. Route cheap turns elsewhere with a combo — trivial edits and naming requests do not need your premium quota. Upgrade the plan if you consistently exhaust it before the cycle ends. Wait for the billing cycle to roll over if none of the above apply.

Shortening prompts or lowering max_tokens. — The limit counts requests, not tokens. A smaller request still costs one. Waiting an hour and retrying. — It resets on the billing cycle, not a rolling window.

Kiro (AWS Q Developer), Amazon CodeWhisperer

Kiro "You have reached the limit" / MONTHLY_REQUEST_COUNT — what to do

Matches these upstream messages

monthly_request_count
reached the limit
servicequotaexceeded

What you actually see

ServiceQuotaExceededException: You have reached the limit
  reason: MONTHLY_REQUEST_COUNT

What does "monthly_request_count" mean?

The account has spent its monthly request allowance. This is a billing-cycle limit, not a per-minute rate limit, so waiting a few minutes does nothing — it resets when the next cycle starts.

Why does it happen?

Agentic tools spend requests fast: every tool call, retry and sub-task is its own request. A single long refactor can burn hundreds without feeling like it.

How do I fix it?

Add a second account. kRouter rotates across accounts automatically, so the work continues on the next one the moment this one is exhausted.
Route cheap turns elsewhere with a combo — trivial edits and naming requests do not need your premium quota.
Upgrade the plan if you consistently exhaust it before the cycle ends.
Wait for the billing cycle to roll over if none of the above apply.

Is it really this error?

These get mistaken for each other, and chasing the wrong one is where the time goes.

Looks like: A rate limit, because both are quota-shaped.

Actually: A rate limit resets in seconds to minutes. This resets on your billing cycle — retrying is pointless for days.

Looks like: Your prompt being too large.

Actually: Size errors name content length. This one counts requests, not tokens: a hundred tiny agent calls exhaust it as fast as a hundred large ones.

What will not fix it

Reasonable-sounding fixes that do not apply here — worth ruling out before you spend an afternoon on them.

Shortening prompts or lowering max_tokens.
The limit counts requests, not tokens. A smaller request still costs one.
Waiting an hour and retrying.
It resets on the billing cycle, not a rolling window.

What kRouter does automatically

kRouter locks the ENTIRE account for 30 days — every model on it, not just the one you asked for. It immediately fails over to your next connected account or provider, so the request still completes.

Stop hitting this error

kRouter routes your AI coding tools across every provider and account you own, so a limit on one does not stop your work. It is free, MIT-licensed and runs on your machine.

Install kRouter