Before you start
-
A capital provider with batch orders on, and its
id, fromGET /v1/batch-orders/capital-providers?network=evm-mainnet: on Ethereum, your stablecoin delegate’s ID. An emptycapitalProviderslist means your organization has none with batch orders on for the network; Get set up says how to get one.Response -
An operator. An admin, or a key with
cp:admin, selects the wallet that executes your orders:Without an operator, users cannot place orders with you. - On Solana, durable nonce accounts for your operator. Each Solana order uses one, and users cannot place orders while the pool is empty. Batch operations explains how to register them.
1. Post capacity, before 4:30 PM
Set how much of a token you will fill in a batch.posted is the total in whole tokens, with at most 6 decimal places, not an increment: 250000 is 250,000 USTB. token is the token’s address. batchId names the batch by its release date: the batch.batchId that GET /v1/batch-orders/capital-providers returns for the batch now taking orders, or a later date.
Response
intakeOpen is about users’ orders only: it is false for a later batch that still takes capacity. Orders reserve capacity as they arrive, so a new total cannot go below what they already reserve.
2. Check what the batch needs
GET /v1/batch-orders/batches/{batchId}/requirements totals the output and protocol fees the batch’s orders need, by capital provider, operator, and token. batchId is the release date, such as 2026-11-06.
Response
3. Retrieve the released orders, at 5:00 PM
GET /v1/batch-orders/payloads returns each released order with its complete signed authorization. Only your organization receives them. The authorization is what the operator executes on-chain, so its assetInAmt and assetOutAmt are in base units: 1000000000 is 1,000 USDC.
Response
4. Execute each order
Your operator executes each order on-chain, targeting 5:15 PM and always before the order’s signed deadline. On Solana, the operator adds its signature to the transaction and sends it.5. Report each outcome, by 5:30 PM
Report every order between the release, at or just after 5:00 PM, and the 5:30 PM close, with areason:
201 with the recorded revision:
Response
underReview until it does. Reports says what each status does to the order.
When something goes wrong
Users cannot prepare orders while you have no operator (
OPERATOR_NOT_SELECTED), or on Solana while your operator has no idle nonce account (NONCE_ACCOUNT_UNAVAILABLE). Errors lists every code.