Get current rate-limit usage
Returns the rate-limit state of both per-subaccount pools (order and cancel) so callers can self-pace and inspect which throttle is constraining them.
{used, cap, nextAvailableMs}:
cap= BaseSeed + lifetime_filled_usd / 10. Lifetime volume is shared across both pools, so the two caps grow in lockstep.nextAvailableMsis 0 whileused < cap. Past the cap, it carries the millisecond-until-next-drip-token (1 action per 10 seconds in production).
Query Parameters
Master Ethereum address for this API key (must match address from POST /createApiKey for the same key). Required on REST for account-scoped reads and for place/cancel. Invalid hex → 400; mismatch with key → 403.
20-byte EVM address as hex: optional 0x or 0X prefix and exactly 40 hexadecimal digits. API responses normalize to lowercase a–f after 0x.
^(0x|0X)?[0-9a-fA-F]{40}$Response
Subaccount rate-limit pool state.
0x-prefixed 40-character hex Ethereum address echoed from the request.
"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb"
Subaccount index echoed from the request (0-9).
0 <= x <= 9Order pool — charges placeOrder / modifyOrder / batchPlaceOrders. BaseSeed: 10,000.
Cancel pool — charges cancelOrder / batchCancelOrders / cancelAllOrders (latter charges 5,000 flat). BaseSeed: 20,000. Independent consumed counter from order; a cancel-heavy pattern can saturate this while order still has headroom.