# Retries and limits

How fast you can call, what to do when you hit the limit, and how to retry a change without doing it twice.

## Rate limits

| Door | Limit |
| --- | --- |
| HTTP API tools | 60 requests a minute per IP |
| MCP | 120 requests a minute per IP |

Every HTTP answer carries `RateLimit-Policy` and `X-RateLimit-Limit`.

## When to retry

- `429` – too many calls this minute. Wait, then retry.
- `500` – something broke on our side. Retry after a pause; if it keeps happening, [tell us](https://pirateskills.com/contact).
- Any other `4xx` – the call itself is wrong. Retrying unchanged gives the same answer; see [Errors](https://pirateskills.com/docs/errors).

## Retrying a change

Send an `Idempotency-Key` header with a tool that changes something. A retry with the same key gets the first answer back (`Idempotent-Replayed: true`) instead of doing it twice. Keys are kept 24 hours. [Example](https://pirateskills.com/docs/http#retries)

---
Source: https://pirateskills.com/docs/limits · All docs: https://pirateskills.com/docs.md · Short overview: https://pirateskills.com/llms.txt