> For the complete documentation index, see [llms.txt](https://docs.themochi.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themochi.app/troubleshooting-and-safety/rate-limits.md).

# Handle rate limits

A **rate limit** caps how many requests an integration can make in a period. When a limit is reached, Mochi returns `429 Too Many Requests` and a `Retry-After` header.

Wait at least the number of seconds in `Retry-After`. Add a small random delay when several workers share a key, so they do not all retry at once. Always limit the number of retry attempts.

For a full `429` decision and safe escalation path, see [Troubleshoot API requests](/troubleshooting-and-safety/diagnose-api-failures.md).

## Current request limits

| Budget                 | Limit                      |
| ---------------------- | -------------------------- |
| Read requests          | 120 per minute per API key |
| Write requests         | 60 per minute per API key  |
| Organization aggregate | 60,000 requests per day    |

Read and write requests use separate per-key minute buckets. All keys and supported API consumers for the same organization share the organization daily budget.

Do not retry `400`, `401`, `403`, or `404` responses automatically. Treat `409` according to the operation's idempotency guidance.

## Additional limits for messages

Outbound messages also have recipient, messaging-window, account, and pacing rules. Staying below the API request limit does not guarantee that Mochi will accept a message.

Confirm the current operation surface in the [canonical OpenAPI contract](https://openapi.gitbook.com/o/M0sgy6xKutCblHRqGmE5/spec/mochi-api.json).


---

# 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.themochi.app/troubleshooting-and-safety/rate-limits.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.