Rate limits

Limit	Value
Requests per key	120 a minute
Write requests per key (prompt endpoints)	20 a minute, within the 120
Failed authentication per address	30 a minute
Request body	256 KB

A request over a limit gets:

HTTP/1.1 429 Too Many Requests
Retry-After: 60

{ "error": { "code": "rate_limited", "message": "Rate limit exceeded…" }, "request_id": "…" }

Wait for the number of seconds in Retry-After, then retry. Every authenticated response carries X-RateLimit-Limit: 120 and X-RateLimit-Policy: 120;w=60. The limiter does not report a remaining count, so pace yourself rather than counting down to zero.

Staying well inside the limits

Ask for less, less often. Data changes once a day, when the daily scan lands. Most integrations need one pull a day.
Use group_by instead of looping. One visibility request grouped by platform and date replaces dozens of single-day calls.
Page with the cursor rather than re-requesting with bigger ranges.
Back off exponentially on 429 and 5xx.

Need more? Email [email protected] with what you are building.

Get started

Discovery

Prompts

Reports

Agent Analytics

Action Center

Staying well inside the limits

​Staying well inside the limits

Staying well inside the limits