Skip to main content

​
When this happens

The tenant has exceeded the rate limit for the called route group. Both analyzer endpoints and administrative endpoints have separate budgets; the response detail tells you which.

​
Example response

​
How to recover

  1. Read Retry-After (seconds).
  2. Sleep for that many seconds (with a small jitter to avoid thundering-herd retries when many callers hit the limit at once).
  3. Retry the request.
The official SDKs do this automatically up to a configurable retry ceiling.

​
How to avoid the limit

  • Distribute heavy workloads. Two API keys in the same tenant share a budget, so multiple keys do not raise the ceiling — they just give you better attribution.
  • Use the smaller default-permissive policy when shadow testing. Permissive policies still cost an analyzer call; if you are running shadow analysis on every prompt, plan capacity for it.
  • Watch X-RateLimit-Remaining. Charting this over time tells you when you are approaching the ceiling.
  • Upgrade your plan. See Billing for the included rates per tier and email sales@lasscyber.com for higher custom limits.

​
SDK behaviour

SDKs sleep for retry_after and retry automatically. If retries are exhausted, the SDK raises RateLimitError with the latest request_id.