Documentation
Rate Limits
Plan integrations with conservative request patterns so simulations, exports, and supporting APIs remain reliable under load.
Documentation
Why limits matter
Message evaluation workflows can be bursty, especially during launches or batch comparisons.
Message evaluation workflows can be bursty, especially during launches or batch comparisons.
Reasonable client-side backoff and queueing protect your integration from avoidable failures.
Teams should design for retries, not assume infinite throughput.
01
Why limits matter
- Message evaluation workflows can be bursty, especially during launches or batch comparisons.
- Reasonable client-side backoff and queueing protect your integration from avoidable failures.
- Teams should design for retries, not assume infinite throughput.
02
Recommended client behavior
- Batch work where possible instead of firing unnecessary parallel requests.
- Use exponential backoff for retryable failures.
- Instrument error rates in staging before increasing traffic in production.