> For the complete documentation index, see [llms.txt](https://docs.api.plenty.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.api.plenty.network/terms-of-use/rate-limit.md).

# Rate Limit

Plenty's Unified API enforces a rate limit of **50 requests per second** on the public link <mark style="color:purple;">**api.plenty.network**</mark>. This means that any application or service utilizing the API is allowed to make up to 50 API requests in a single second.

This rate limit is put in place to ensure fair and efficient usage of the API, preventing any single user or application from overloading the system with an excessive number of requests. Adhering to this rate limit is essential for maintaining the stability and reliability of Plenty's Unified API for all users and applications.

Developers should be mindful of this rate limit when designing their applications and implement proper rate-limiting mechanisms to ensure they do not exceed the allowed request rate. **Additionally, it's essential to monitor and adjust your application's usage of the API to stay within these limits and avoid disruptions in service.**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.api.plenty.network/terms-of-use/rate-limit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.