Skip to main content
err:frontline:client:usage_exceeded
The API you called runs on Unkey, and each request spends credits from your API key. Your key has no credits left for this one. You get 429 Too Many Requests.
Example response
Browsers get the same error as an HTML page.

​
If you’re calling an API hosted on Unkey

Retrying won’t help until the owner adds credits or a scheduled refill runs. There’s no Retry-After header for this error. Contact the API owner with the request ID and ask about your quota.

​
If you own this API

Each request that passes a key-auth policy costs the policy’s credits value, or 1 if it isn’t set. Gateway traffic and your own keys.verifyKey calls spend from the same balance on the key. Common causes:
  • The key used up its credits.
  • A route that shouldn’t be metered is costing credits.

​
How to fix

  1. Add credits with keys.updateCredits, set up a refill so the balance tops up on a schedule, or remove the credit limit from the key.
  2. For a route that shouldn’t cost credits, set credits: 0 on its policy and create a new deployment.
A negative credits value makes every matched request fail with invalid_configuration.
Last modified on October 6, 2026