describing which rate limit was exceeded, along with a retry-after header indicating how long to wait.
Anthropic Rate Limits → · 2026-10-14T11:59:32.305Z
- describing which rate limit was exceeded, along with a `retry-after` header indicating how long to wait. + describing which rate limit was exceeded. When the response has a `retry-after` header, wait that many seconds before retrying. - Rate limits are applied separately for each model; therefore you can use different models up to their respective limits simultaneously. You can check your current rate limits and behavior on the [Rate limits](https://docs.anthropic.com/usage/limits) + Each row in the following tables has its own RPM, ITPM, and OTPM limits. Some rows cover several models that share one limit; see the notes under the tables. You can check your current rate limits and behavior on the [Rate limits](https://docs.anthropic.com/usage/limits) - | `retry-after` | The number of seconds to wait until you can retry the request. Earlier retries will fail. Not sent with the spend-cap 429 (see [Reaching your spend cap](https://docs.anthropic.com/en/api/rate-limits#reaching-your-spend-cap)<br>). | + | `retry-after` | The number of seconds to wait until you can retry the request. Earlier retries will fail. Not every 429 carries it; the spend-cap 429 never does (see [Reaching your spend cap](https://docs.anthropic.com/en/api/rate-limits#reaching-your-spend-cap)<br>). |