Rate Limits

The edge API currently emits informational traffic counters. Integrations should bound concurrency and handle throttling responses when received, while treating these counters separately from an enforced service quota.

Response Headers

Successful responses carry:

  • X-RateLimit-Limit — currently 1000 for the informational counter.
  • X-RateLimit-Remaining — decremented on requests and clamped at zero.
  • X-RateLimit-Reset — the counter's reset time as Unix seconds. Its window lasts 60 seconds from initialization or the last reset.

Counters are local to each API process and keyed by bearer token. They are not a shared budget across instances or all tokens belonging to an actor. Do not assume these headers are present on error responses or that a zero remaining value will produce 429 or Retry-After.

Retry Behavior

  • If a response supplies Retry-After, wait for the specified delay. Otherwise use bounded exponential backoff with jitter for retryable 429, 502, or 503 responses.
  • Reuse the same idempotency key and request body when retrying a create that supports idempotency. See Idempotency And Concurrency.
  • Keep concurrency and retry counts bounded so repeated failures do not create an unbounded queue of requests.