What are the API rate limits?
Rate limits apply to Agenta Cloud. If you self-host the open-source edition, Agenta does not enforce any rate limits; capacity is set by your own infrastructure. In self-hosted Enterprise deployments, limits are configured per deployment.
Agenta Cloud limits requests per organization. Limits vary by plan and endpoint type.
Each limit has two values. Burst is the number of requests you can send back to back when you have not made requests recently. Refill is the number of requests added back to your budget per minute, which sets the sustained rate. Each endpoint type has its own budget, so using up one does not affect the others.
Cells show burst / refill per minute.
| Endpoint type | Example | Hobby | Pro | Business | Enterprise |
|---|---|---|---|---|---|
| Configuration fetching and trace ingestion | POST */retrieve, POST /otlp/v1/traces | 1,200 / 1,200 | 3,600 / 3,600 | 36,000 / 36,000 | Custom |
| Trace queries and analytics | POST /tracing/spans/query, POST /tracing/spans/analytics | 120 / 1 | 180 / 1 | 1,800 / 1 | Custom |
| AI services | POST /ai/services/tools/call | 10 / 30 | 30 / 90 | 300 / 900 | Custom |
| All other endpoints | General API calls | 480 / 480 | 1,440 / 1,440 | 3,600 / 3,600 | Custom |
Rate limit response
When you exceed the rate limit, the API returns 429 Too Many Requests.
{
"detail": "Rate limit exceeded. Please retry after 5 seconds."
}
The response includes headers that help you back off:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed (burst capacity) |
X-RateLimit-Remaining | Remaining requests in the current window |
Retry-After | Seconds to wait before retrying. Only returned on 429 responses. |
Successful responses also include X-RateLimit-Remaining.