> For the complete documentation index, see [llms.txt](https://developer.jylo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.jylo.ai/rate-limiting.md).

# Rate Limiting

#### Fixed Window Rate Limiting

In Jylo, a fixed window of 1 minute is applied, during which a client can make up to 100 requests. If a client exceeds these 100 requests within the minute, all subsequent requests will be denied with an HTTP 429 (Too Many Requests) status code for the remainder of the time window.

#### Client-Side Rate Limiting Tips

* **Implement Request Queuing:** Queue your requests and release them gradually to avoid breaching the rate limit.
* **Adaptive Request Timing:** Dynamically adjust the rate of requests based on server responses, ensuring requests are always below the threshold limit.
* **Exponential Backoff Strategy:** On receiving a 429 status code, increase the wait time gradually before retrying, to ease pressure on the server.


---

# 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://developer.jylo.ai/rate-limiting.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.