> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.dyspach.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate limits

> How request throttling works and how to handle it.

Requests are rate limited **per organisation** using a fixed 60-second window.

<CardGroup cols={2}>
  <Card title="Default" icon="gauge">
    **60 requests / minute** per organisation (across all your keys).
  </Card>

  <Card title="Per-account override" icon="sliders">
    Need more? Dyspach can raise the limit for your account.
  </Card>
</CardGroup>

## Response headers

Every response includes your current window state:

```http theme={null}
RateLimit-Limit: 60
RateLimit-Remaining: 42
RateLimit-Reset: 23
```

<ResponseField name="RateLimit-Limit" type="integer">Requests allowed in the current window.</ResponseField>
<ResponseField name="RateLimit-Remaining" type="integer">Requests remaining in the current window.</ResponseField>
<ResponseField name="RateLimit-Reset" type="integer">Seconds until the window resets.</ResponseField>

## When you're throttled

You receive `429 Too Many Requests` with a `Retry-After` header:

```http theme={null}
HTTP/1.1 429 Too Many Requests
Retry-After: 23
```

```json theme={null}
{ "message": "Rate limit exceeded", "limit": 60, "retryAfterSeconds": 23 }
```

<Tip>
  Back off for `Retry-After` seconds, then retry. Read `RateLimit-Remaining` to
  pace yourself and avoid hitting the limit at all.
</Tip>