For market makers
Inventory, order controls, streaming, and recovery patterns for liquidity providers.
Market makers use the same order, portfolio, and streaming APIs as other traders. The difference is how often you quote, how you reserve inventory, and how you recover after stale state.
This section focuses on:
- Inventory: how binary YES/NO tokens are minted, reserved, and merged.
- Operations: post-only orders, self-trade prevention, asynchronous cancellation, and quote-loop sizing.
- Recovery: rebuilding authoritative state after a restart or missed stream messages.
- Pre-signed orders: signing locally for strategies that need the dedicated signed-order endpoint.
- Account batches: signing atomic position and withdrawal operations.
These guides cover AGARA markets. Every market is binary, including each member of a neg-risk event.
Controls you will use
| Capability | Where to look |
|---|---|
| Post-only orders | Orders → post-only |
| Cancel-maker self-trade prevention | Self-trade prevention |
| Time-bounded GTD orders | Orders → time in force |
| Cancel every open order | Orders → cancel everything open |
| Private fills, acknowledgements, and cancellations | Account stream |
| Public orderbook and quote updates | Streaming |
Important limits
- A SELL order always requires and reserves the outcome shares being sold.
- A BUY order reserves collateral and its worst-case fee requirement.
- Complementary YES BUY and NO BUY orders can settle by minting a new pair; this does not make a conventional BUY/SELL quote inventory-free.
- Split and merge accept PATs with their respective position scopes; self-custody clients can combine inventory and withdrawal operations in a signed account batch.
- The platform does not cancel resting orders when your WebSocket disconnects. Reconcile and use cancel-all when your local state is uncertain.
Start with Inventory, then implement the quote loop and recovery flow.