id in every swap and batch order route. Stablecoin delegates describes the contract, and Administer your delegate shows how to change its configuration through the API.
On Ethereum mainnet, Multiliquid assigns delegates to your organization; on evm-sepolia, an admin can also deploy them in the Multiliquid app. An admin names deployed delegates and turns batch orders on or off for each in the app. A deployed delegate starts with batch orders off, and until they are first turned on it is not a batch order capital provider: the capacity and operator routes answer 404 with NOT_FOUND, and preparation answers UNKNOWN_CAPITAL_PROVIDER. When they are turned off later, the delegate is absent from the batch order listings, new orders and capacity updates are rejected with BATCH_ORDERS_DISABLED, operator selection and clearing still apply, and accepted orders keep their release, payloads, reports, and outcomes.
Your organization ID
The delegate list takes your organization’s ID.GET /v1/organization returns the organization the credential acts for, its id and name, and no other. It takes any API key, personal or organization, of any scope, or an account session with a selected organization, and no parameters.
Response
Cache-Control: no-store, and no rate-limit headers.
Listing your delegates
GET /v1/organizations/{organizationId}/delegates?network=evm-mainnet lists every delegate your organization owns on the network, ordered by delegate ID: committed assignments and completed deployments. It takes an account session of any member, or an API key of the organization with read, and serves evm-mainnet and evm-sepolia. Another organization in the path is a 404.
$ORGANIZATION_ID to the id above. The response holds delegates, the whole list on one page, with no nextCursor. Each has:
A deployed delegate whose stablecoin Multiliquid no longer lists stays in the list as
notSwappable, and takes no swaps or orders.
Admin state
GET /v1/organizations/{organizationId}/delegates/{delegateId}/admin/state?network=evm-mainnet reads a delegate’s configuration as it is on-chain now. It takes an account session of any member, or an API key of the organization with read, and serves evm-mainnet and evm-sepolia, by those keys only. delegateId is the delegate’s ID, a 0x-prefixed 32-byte hex string. Administer your delegate shows a request and its response, which carries Cache-Control: no-store.
Four optional query parameters each check one address, and add the matching field to the response:
The response has:
Every address is lowercase hex. Every value comes from the same block. Fee and discount rates are not part of the admin state.
Preparing an admin action
POST /v1/organizations/{organizationId}/delegates/{delegateId}/admin/prepare returns the unsigned transaction that makes one change to a delegate, with checks of whether it would succeed now. It takes an account session of an admin, or an API key of the organization with cp:admin, and serves evm-mainnet and evm-sepolia, by those keys only. The body is at most 1 KiB. Administer your delegate shows a request and its responses, which carry Cache-Control: no-store.
Preparing stores nothing and changes nothing on-chain. Your capital provider admin wallet signs the transaction and sends it to the network; Multiliquid never signs or sends it.
The body has:
Admin actions
Every address is a nonzero Ethereum address. A rate israteBps, a whole number of basis points below 10000 (100%): 10 is 0.1%, and 1 is 1 basis point. An RWA ID or stablecoin ID is a 0x-prefixed 32-byte hex string, as deployment info lists. Stablecoin delegates describes the effect of each change on-chain.
For example, a delegate is paused with
{"type": "pause"}, and a custody address is set with {"type": "setStablecoinCustodyAddress", "custodyAddress": "0x…"}.
Prepare response
A failing check never fails the request; it answers
200 with the check failing, so you can see what to fix. Don’t send a transaction whose checks fail: it reverts on-chain.