limit_exceeded — subscription usage limit exceeded

The third of the five 429 sources. The body has only message and reason — neither the token quota fields (window/limit/used) nor a Retry-After header.

The limit belongs to the subscription, not the key: it caps account consumption over the billing period of the plan. Switching keys will not help here — all keys on the account hit the same counter.

Telling it apart from the token quota is simple: that one has Retry-After and window numbers; this one has nothing. Backoff will not help until the period ends: you need to wait for period_end, not "a couple of minutes". The quick ways out are a different plan or an add-on package.

GET /usage — the limit entries have period_start, period_end, and resets_in; they show how long to wait. For a specific service — GET /usage/{service}.

• Guide: limits and the 429 code
• token_quota_exceeded — key limit, not subscription limit
• GET /usage
• GET /usage/{service}
• Account limits
• Change plan