- Request rate limit - how many requests your workspace can send per minute.
- Concurrent stream limit - how many streaming responses your workspace can hold open at once.
What you see when a limit is hit
Both limits return an OpenAI-compatible error body.Retry-After header with the number of seconds until your window resets.
How enforcement works
Both limits are checked at the edge before the request is forwarded. A request that exceeds either limit is rejected immediately with a429. An open streaming response counts against your concurrent limit until it finishes.
If the enforcement backend is briefly unavailable, requests are allowed through rather than blocked. Toolken prioritizes availability over hard-blocking during transient disruptions.
Handling 429s in your code
A429 from Toolken is safe to retry. Read Retry-After and wait that many seconds before the next attempt. For agent loops that fire many parallel requests, add a concurrency limit on the client side to stay within the per-workspace ceiling.
Next
Observability
Track request volume and spend before you hit a limit.