Getting started

Rate limits

Limits are enforced per consumer at the gateway. WebSocket connections count against a separate concurrency budget.

Per-tier limits

  • Free: 60 requests / minute.
  • Builder: 600 requests / minute.
  • Pro: 3,000 requests / minute.

See Access tiers for the full surface matrix.

Response headers

Every response carries your current budget:

http
RateLimit-Limit: 600
RateLimit-Remaining: 583
RateLimit-Reset: 41

Handling 429

Over the limit returns 429 Too Many Requests with a Retry-After header (seconds). Back off and retry — prefer exponential backoff with jitter.

Prefer streams over polling

If you're polling snapshots or history on a tight loop, use the matching authenticated WebSocket stream when your plan includes it. One connection replaces repeated requests and stays under budget. See Live APIs for deployed paths.