> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.next-dev.rtcleague.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.next-dev.rtcleague.com/_mcp/server.

# Rate limits

Each API key has its own rate-limit budget. By default:

* **60 requests per minute**
* **1,000 requests per hour**

These are per-key, sliding-window limits. If you hit the limit you'll get a
`429 Too Many Requests` response with a `Retry-After` header telling you how
many seconds to wait.

## Response headers

Every successful request (and most error responses) includes:

| Header                         | Meaning                                     |
| ------------------------------ | ------------------------------------------- |
| `X-RateLimit-Limit-Minute`     | Your per-minute limit.                      |
| `X-RateLimit-Remaining-Minute` | Requests left in the current minute window. |
| `X-RateLimit-Reset-Minute`     | Seconds until the minute window resets.     |
| `X-RateLimit-Limit-Hour`       | Your per-hour limit.                        |
| `X-RateLimit-Remaining-Hour`   | Requests left in the current hour window.   |
| `X-RateLimit-Reset-Hour`       | Seconds until the hour window resets.       |

## When you exceed a limit

```http
HTTP/1.1 429 Too Many Requests
Retry-After: 12
Content-Type: application/json

{
  "error": {
    "type": "rate_limit_error",
    "code": "rate_limit_per_minute",
    "message": "Rate limit exceeded: 60 requests per minute. Retry in 12s."
  }
}
```

## Handling

* Honor the `Retry-After` header — it's the simplest correct strategy.
* For batch workloads, use the `X-RateLimit-Remaining-*` headers to pace
  yourself proactively instead of waiting for a `429`.
* Use exponential backoff if you see repeated `429`s — they suggest you're
  hammering the limit faster than the window resets.

## Need higher limits?

If your use case requires more, contact us — we can set per-key overrides via
`rate_limit_per_minute` and `rate_limit_per_hour` columns. Reach out at
**[support@telecho.io](mailto:support@telecho.io)** with your expected request profile.