Skip to main content

Rate Limits

Gildea uses fixed-window rate limiting on both per-minute and monthly windows.

Limits by tier

TierRequests/minRequests/month
Hacker (Free)5200
Pro302,000
Team12010,000
Monthly limits use a rolling 30-day window.

Rate limit headers

Every authenticated response includes rate limit headers:
X-RateLimit-Limit-Minute: 30
X-RateLimit-Remaining-Minute: 28
X-RateLimit-Limit-Monthly: 2000
X-RateLimit-Remaining-Monthly: 1847

When you’re rate limited

If you exceed your limit, the API returns 429:
{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Rate limit exceeded",
    "status": 429
  }
}
The response includes a Retry-After header (in seconds):
Retry-After: 60

Best practices

  1. Check remaining counts — use the X-RateLimit-Remaining-* headers to throttle proactively
  2. Respect Retry-After — wait the indicated time before retrying
  3. Use pagination — fetch fewer, larger pages instead of many small requests
  4. Cache responses — signal data doesn’t change frequently