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