> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/settings/security/rate-limiting.md).
# Rate Limiting
**Introduction to rate limiting**\
Rate limiting plays a crucial role in enhancing the security and efficiency of your API. By limiting the number of requests that can be made to your API within a specific timeframe, you achieve several key benefits
1. Manage and control the volume of network
2. Acts as a defense mechanism against abusive or malicious activities.
3. By preventing excessive requests, rate limiting ensures server resources are used efficiently.
**Implementation in Limio**
Limio provides the flexibility to set specific rate limits and periods for various types of requests to the Limio API, including:
1. **Payment -** Set limits when generating payment tokens and token endpoints for subscription management platforms like Zuora
2. **Payment Basket -** Set limits when generating payment tokens for subscription management platforms like Zuora
3. **Order Requests -** Set limits on functions calling APIs during order processing
To configure these limits go to General Settings > Site Security
---
# 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.limio.com/product/settings/security/rate-limiting.md?ask=&goal=
```
`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.