Rate Limits
Rate limits control how many requests or compute units (CUs) you can send to our APIs over a given period. These limits help protect platform stability, ensure fair access for all users, and manage system load.
You can monitor your current usage and limits from the Dashboard – Usage page (login required).
Why Rate Limits Exist
We use rate limits to:
- ✅ Prevent misuse or overload of shared infrastructure
- ✅ Ensure fair usage across all customers
- ✅ Maintain performance during high traffic
Types of Limits
| Type | Description |
|---|---|
| Request-based | Limits the number of requests per second (RPS) or minute (RPM). |
| Compute Unit (CU) | Each API call consumes a specific CU weight based on the request. See Compute Units page for reference. |
Product Rate Limits
Product | Limit Type | Values | Notes |
|---|---|---|---|
Staking API | Requests/min | 250 RPM | Enforced at the entry point. Contact support to raise the limit. |
Staking Reporting API | Compute Units | 1 CU per request | Applies to all protocols and endpoints. |
RPC API | Requests/sec | Free: 5 RPS | Based on your current plan. All endpoints follow the same limit. |
REST API | Requests/sec | Same as RPC tier | Same as RPC tier |
Dedicated Nodes | — | — | We do not apply rate limits to any of our dedicated nodes. |
DeFi API | Varies | Based on the plan tier. | See Expand pricing for details. |
When You Hit a Rate Limit
When your request exceeds the allowed request or CU limits, the API returns a 429 Too Many Requests error:
{
"type": "too-many-requests",
"title": "Too Many Requests",
"status": 429,
"detail": "Request rate limits have been exceeded. Try again after a few seconds."
}Best Practices
- Send multiple operations in one request if supported.
- Cache frequent responses to reduce redundant calls
- Minimize redundant calls for repeated data.
Updated 26 days ago