Guide
Rate Limits
Request rate limits on the ORN API: the standard class, how limits are counted and what a 429 response means.
The standard rate limit
All operations today belong to the standard rate limit class: 60 requests per 60-second window, counted per credential. The limit is enforced independently of your wallet balance and free allowance — it protects the platform for everyone and is not a billing control.
| Class | Requests | Window | Counted per |
|---|---|---|---|
| standard | 60 | 60 seconds | Credential |
If an operation were ever assigned a different class, its reference page in API Operations would say so. Any unknown class fails closed to the standard limit.
When you hit the limit
Requests beyond the limit are rejected with 429 RATE_LIMITED before billing — a rate-limited call is never charged. The rejection happens early in the request pipeline (after authentication and authorization, before the free allowance and wallet debit), so hitting the limit has no billing effect.
{
"code": "RATE_LIMITED",
"error": "Too many requests. Slow down and retry.",
"request_id": "…"
}- Retry with exponential backoff and jitter rather than fixed tight loops.
- Spread scheduled workloads (for example monitoring polls) across the window.
- A rate-limited request still consumes nothing: no charge, no allowance use.