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

# Rate Limiting

To ensure fair usage and protect the API from abuse, rate limiting is applied.

* **Limit:** 60 requests per minute per IP address.
* **Headers:** Standard rate limit headers (`RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset`, `Retry-After`) are included in responses according to the [IETF Draft standard](https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-ratelimit-headers-08).
* **Exceeding Limit:** If you exceed the rate limit, you will receive an HTTP `429 Too Many Requests` response. Check the `Retry-After` header to see when you can make requests again.

**Example 429 Response:**

```http
HTTP/1.1 429 Too Many Requests
RateLimit-Limit: 60
RateLimit-Remaining: 0
RateLimit-Reset: 45  // Seconds until the limit resets
Retry-After: 45      // Seconds to wait before retrying
Content-Type: application/json

{
  "error": "You can only make 60 requests every minute."
}
```


---

# 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.blog-api.codewithsadee.com/guides/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.
