Skip to main content
Duckie API rate limits use one-minute windows. Every authenticated request is checked against layered limits.
BucketDefault limit
Missing or invalid key attempts60 requests/minute/IP
Global key traffic5,000 requests/minute/key
Global organization traffic25,000 requests/minute/organization
Runs list600 requests/minute/key
Run tool options600 requests/minute/key
Run detail2,400 requests/minute/key
Tools, agents, guidelines, guardrails, and runbooks2,400 requests/minute/key

​
Rate-Limit Headers

Successful authenticated responses include rate-limit headers for the active limiting bucket. 
X-RateLimit-Limit: 600
X-RateLimit-Remaining: 599
X-RateLimit-Reset: 1780444830
HeaderMeaning
X-RateLimit-LimitRequest limit for the active bucket
X-RateLimit-RemainingRequests remaining in the current window
X-RateLimit-ResetUnix timestamp when the bucket resets

​
Rate-Limited Responses

When a request exceeds a limit, Duckie returns 429 rate_limited. 
HTTP/1.1 429 Too Many Requests
Retry-After: 12
X-RateLimit-Limit: 600
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1780444830

{
  "error": {
    "code": "rate_limited",
    "message": "Rate limit exceeded",
    "request_id": "req_123",
    "retry_after": 12
  }
}
Wait at least the Retry-After number of seconds before retrying. If you are exporting a large data set, keep using cursor pagination and back off when X-RateLimit-Remaining gets low.