---
updatedAt: 2026-05-11T12:28:32.000Z
---

Fetch the complete documentation index at: https://docs.blockdaemon.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# 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](https://docs.blockdaemon.com/docs/api-suite-dashboard#usage) (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](https://docs.blockdaemon.com/docs/compute-units) page for reference. |

## Product Rate Limits

<Table>
  <thead>
    <tr>
      <th>
        Product
      </th>

      <th>
        Limit Type
      </th>

      <th>
        Values
      </th>

      <th>
        Notes
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Staking API**
      </td>

      <td>
        Requests/min
      </td>

      <td>
        250 RPM
      </td>

      <td>
        Enforced at the entry point. Contact support to raise the limit.
      </td>
    </tr>

    <tr>
      <td>
        **Staking Reporting API**
      </td>

      <td>
        Compute Units
      </td>

      <td>
        1 CU per request
      </td>

      <td>
        Applies to all protocols and endpoints.
      </td>
    </tr>

    <tr>
      <td>
        **RPC API**
      </td>

      <td>
        Requests/sec
      </td>

      <td>
        Free: 5 RPS<br />Starter: 100 RPS<br />Growth: 200 RPS<br />Enterprise: Custom
      </td>

      <td>
        Based on your current plan. All endpoints follow the same limit.
      </td>
    </tr>

    <tr>
      <td>
        **REST API**
      </td>

      <td>
        Requests/sec
      </td>

      <td>
        Same as RPC tier
      </td>

      <td>
        Same as RPC tier
      </td>
    </tr>

    <tr>
      <td>
        **Dedicated Nodes**
      </td>

      <td>
        —
      </td>

      <td>
        —
      </td>

      <td>
        We do not apply rate limits to any of our dedicated nodes.
      </td>
    </tr>

    <tr>
      <td>
        **DeFi API**
      </td>

      <td>
        Varies
      </td>

      <td>
        Based on the plan tier.
      </td>

      <td>
         See [Expand pricing](https://www.expand.network/pricing)  for details.
      </td>
    </tr>
  </tbody>
</Table>

## 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:

```json
{
  "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.