Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Batch

POST /v1/batch
This route sends up to 256 orders and cancels from one maker as one unit. Every member is checked before anything is sent, and the members are sequenced together with nothing from anyone else between them, which is how to cancel and replace a quote without a gap.
Request
{ "items": [ { "cancel": { "maker": "0x1111…", "nonce": 3, "orderNonce": 1 }, "signature": "0x…" }, { "order": { "maker": "0x1111…", "nonce": 4, "…": "…" }, "signature": "0x…" } ] }
Each item is either {"order", "signature"} or {"cancel", "signature"}, signed exactly as it would be on its own. An order item may add "ioc": true (immediate-or-cancel), as on its own.
202 Accepted
{ "status": "accepted", "clientIds": [3, 4] }
Outcomes arrive on the stream. If any member fails the gateway's checks, nothing is sent, and the 422 names the first failing member: "member 1: price is off the ladder".
A batch costs the sum of its members against the address's signed rate: one for each order and an eighth for each cancel. Its orders' sizes together must fit the account's fill bucket, so an ordinary account's batch holds at most 100 contracts of orders. A batch that could never fit is a 422 by name; one that fits but finds the bucket short is a 429 with Retry-After.