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

# Rate limits

Rate limits are enforced **at the edge**, in front of the venue, per IP:

| Routes                                    | Limit                                     |
| ----------------------------------------- | ----------------------------------------- |
| `/v1/order`, `/v1/cancel`, `/v1/withdraw` | 60 requests / minute                      |
| `/v1/auth/*`                              | 10 requests / minute (signature grinding) |
| Everything else under `/v1`               | 300 requests / minute                     |
| `/ws`                                     | 10 new connections / minute               |

`GET /v1/reserves` stays generously limited on purpose: it is the number a counterparty checks when they are already nervous, and throttling it during an incident reads as hiding.

## The one 429 is not a rate limit

The venue returns exactly one `429`, and it is **overload backpressure**: a session key spent more nonces inside the 60-second freshness window than the venue will remember. The body is `too many orders in flight — retry`.

Retry it. It is not a credential problem and **not** a reason to re-approve a session. No `Retry-After` header is set. An earlier version of this page said no endpoint returns `429`; that stopped being true when session signing landed.

## Practical guidance

**Polling.** [`/v1/chain`](/api-reference/info.md#chain) is the expensive read — it prices a whole expiry. Poll it no faster than once a second per expiry you are displaying, and only for the expiry actually on screen. [`/v1/meta`](/api-reference/info.md#meta) is cheap; a few seconds is plenty.

**Account views.** [`/v1/me`](/api-reference/exchange.md#account) caps the orders it returns at 500 while `openOrderCount` stays exact. It is a view for humans and dashboards, not a synchronisation primitive: do not rebuild your order state from it in a loop.

## Limits that do exist

These are risk limits, not rate limits, and they reject orders rather than throttle requests:

* Buying power must cover premium **and** the taker fee.
* A short must post margin against a **20%** adverse move in the underlying, floored at **10% of strike**.
* Below the **12%** maintenance shock (floored at 6% of strike), an account becomes reduce-only and is eligible for the liquidation sweep.
* At most **16** withdrawals may be outstanding at once.

See [Error responses](/api-reference/errors.md) for what each looks like on the wire, and [market structure](/protocol/market-structure.md) for the full margin formula — note that the floors are fractions of strike, not amounts in cents.


---

# 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.strikelabs.app/api-reference/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.