Documentation Index
Fetch the complete documentation index at: https://docs.lasscyber.com/llms.txt
Use this file to discover all available pages before exploring further.
| HTTP status | 429 Too Many Requests |
| Code | rate_limit_exceeded |
| Retry? | Yes — sleep for Retry-After seconds, then retry. |
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
- Read
Retry-After(seconds). - Sleep for that many seconds (with a small jitter to avoid thundering-herd retries when many callers hit the limit at once).
- Retry the request.
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-permissivepolicy 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.comfor higher custom limits.
SDK behaviour
| SDK | Exception |
|---|---|
| Python | agnes.RateLimitError with retry_after: int |
| TypeScript | RateLimitError with retryAfter: number |
retry_after and retry automatically. If retries are
exhausted, the SDK raises RateLimitError with the latest
request_id.