> For the complete documentation index, see [llms.txt](https://docs.cspr.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cspr.cloud/1.5.x/documentation/overview/rate-limits-and-quotas.md).

# Rate limits and quotas

At CSPR.cloud, we distinguish between rate limits and quotas to ensure efficient API management.

## Rate limit

We impose a limit on the number of requests per minute. This measure helps manage load and avoid overloading our systems.

## Quotas

Quotas control the overall call rates over an extended period, often tied to subscription tiers.

* **Long-term Management:** Quotas determine the total number of calls that can be made in a set period, like a month.
* **Tier-based Access:** For example, a free tier might allow 10,000 calls per month, while a premium tier could permit up to 10,000,000 calls in the same timeframe.

Exceeding these limits triggers a 429 error, signaling a rate limit breach.

## Free tier limits

The free tier limits are set to ensure that you can test the API and integrate it into your application.

### Mainnet

| Service             | Monthly quota | Daily quota | Rate limit /min |
| ------------------- | ------------- | ----------- | --------------- |
| CSPR.Node Proxy     | 20,000        | 1,200       | 100             |
| CSPR.Node Proxy SSE | 5,000         | 200         | 10              |
| CSPR.Cloud API      | 100,000       | 6,000       | 100             |

### Testnet

| Service             | Monthly quota | Daily quota | Rate limit /min |
| ------------------- | ------------- | ----------- | --------------- |
| CSPR.Node Proxy     | 20,000        | 1,200       | 100             |
| CSPR.Node Proxy SSE | 5,000         | 200         | 10              |
| CSPR.Cloud API      | 100,000       | 6,000       | 100             |

## Handling limits

To effectively manage your API usage and comply with rate limit or quota, consider the following strategies:

* **Upgrade to Premium Tier:** If your needs exceed the free tier quota, consider upgrading to our Premium tier for higher limits. You can apply at [CSPR.cloud](https://cspr.cloud).
* **Implement a Backoff-Retry Strategy:** In cases where you encounter a 429 error (rate limit or quota exceeded), it's advisable to implement a backoff-retry strategy. This involves reducing the frequency of your API requests to stay within the allowed limits.
* **Monitor API Calls:** Utilize logging tools to monitor your application’s API usage. This can help you identify patterns and optimize your request strategy to ensure efficient usage.
* **Lazy Loading Technique:** To reduce unnecessary API calls, implement lazy loading in your application. Trigger API calls based on user interactions, such as clicking a button or reaching a specific section of a page, to minimize the number of requests.

Adhering to these strategies will help you efficiently manage your API usage within the CSPR.cloud environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cspr.cloud/1.5.x/documentation/overview/rate-limits-and-quotas.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.