Keys & spend policies

Each API key carries its own limits. They are enforced before any provider is asked to quote, so a blocked order never reaches the market.

PolicyEffect
Read-onlyThe key can list fills, fetch results and export statements, but cannot post orders or settle payments.
Max per orderOrders with a max_price above this are rejected with over_max_per_order.
Daily budgetThe sum of today's matched fill prices (UTC) plus the new order's maximum must stay within the budget. Expired fills do not count.
Allowed typesOnly these request types may be posted. Empty means all types.

Idempotency

Send an Idempotency-Key header (up to 128 characters) when posting an order. If a request with the same key from the same API key already created an order, that order is returned instead of a new one, so network retries never double-spend.

Key storage

Keys are shown once, at creation. We store only a SHA-256 hash. Revoking a key takes effect immediately.

Wallet binding

A key acts for the wallet that created it. Payments for orders posted with the key must be signed by that same wallet, which gives finance teams a single on-chain address to monitor per key owner.