List the asset vaults on a chain
Returns every vault Aqua0 runs on a chain (one vault per asset) with its aggregate totals (principal, deployed, credit) and whether the indexer has caught up. Query parameter: chainId (required).
Authorization
ApiKeyAuth In: header
Query Parameters
Numeric ID of the chain to query or act on.
Response Body
curl -X GET "https://example.com/api/vaults?chainId=string"List the chains Aqua0's vaults are available on
Returns the chains the caller's network mode can see, each with its deployment provenance. In mainnet mode only chains carrying a real mainnet deployment are returned, and in testnet mode every forked chain is. Clients should drive chain pickers from this list rather than a local list, so an undeployed chain is never offered. Fields per chain: chainId, network ('mainnet' or 'fork'), and fleetLive (whether the vaults are both deployed and reachable right now).
Build calldata to lock liquidity into a vault
Returns the transaction calldata the LP signs and sends to lock liquidity into an asset vault. The backend holds no key and produces no signature here; it only builds calls. The response has two legs when a token approval is needed and one when the allowance already covers it (send them in order). Path parameters: chainId and asset (address or symbol). Body: amount (integer string, required), owner (vault-owner / position identity, required), receiver (credited party, optional, defaults to owner), sourceAddress (funding wallet that SENDS the tx and whose tokens are pulled, optional, defaults to owner). The returned `sender` is the wallet that must send the calldata.