Rate limiting is planned and not yet enforced. No endpoint answers
429 Too Many Requests today, and responses carry no X-RateLimit-* or
Retry-After headers. This page will describe the limits and headers
once they ship; that change will be announced in the
changelog.GET /v1/me already reports your organization’s tier under
capabilities.rateLimitTier (STANDARD, HIGH_VOLUME or ENTERPRISE).
The value is informational until limits are enforced.
Until then
Build your client as if limits existed:- Don’t busy-loop retries; back off with jitter after errors.
- Retry writes with the same
Idempotency-Keyand body, so a retry never creates a duplicate. See Idempotency.
Next
Error reference
Every status the API answers today.
Idempotency
Safe retries via
Idempotency-Key.