Rate Limits

All Hype Doc endpoints are rate-limited to ensure fair usage.

Limits by endpoint

Endpoint	Limit	Scope
Authenticated API (/api/v1/*)	100 requests/minute	Per API token
MCP server (/mcp)	60 requests/minute	Per OAuth token
Unauthenticated API	10 requests/minute	Per IP address

Response headers

Every API response includes rate limit headers:

Header	Description
X-RateLimit-Limit	Maximum requests allowed in the current window
X-RateLimit-Remaining	Requests remaining in the current window
X-RateLimit-Reset	Unix timestamp when the current window resets

Throttled responses

When you exceed the rate limit, the API returns 429 Too Many Requests:

HTTP/1.1 429 Too Many Requests
Content-Type: application/json
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1709312400
Retry-After: 45

{
  "error": "Rate limit exceeded. Retry after 45 seconds."
}

Headers on throttled responses

Header	Description
X-RateLimit-Limit	Maximum requests per window
X-RateLimit-Remaining	Always 0 when throttled
X-RateLimit-Reset	Unix timestamp when the window resets
Retry-After	Seconds until you can retry

Best practices

• Check X-RateLimit-Remaining before making requests
• Respect Retry-After headers — don’t retry immediately
• Use exponential backoff if you hit rate limits repeatedly
• For bulk operations, space requests evenly across the window