Automate & Agentic Liquidity

Aqua is a good substrate for headless and agent-driven liquidity because a maker keeps custody the whole time: the SDK builds calldata, the maker's own wallet signs, and you broadcast it through your own RPC. No 1inch component ever holds keys or tokens.

The headless maker loop (live today, zero build)

  1. Monitor strategy health and coverage via your own RPC and the on-chain event log.

  2. Buildship()/dock() calldata with @1inch/aqua-sdk (program + predicted strategyHash).

  3. Sign in the maker wallet.

  4. Broadcast the signed transaction through your own RPC provider.

  5. Confirm via Shipped/Docked/Pulled/Pushed/Swapped events.

Keeper / re-ship on illiquidity

Underfunded strategies are never paused or liquidated on-chain — they simply stop filling (a Coverage effect). Because strategies are immutable, the rebalance primitive is dock() then ship(), producing a new strategyHash. LP fees auto-compound via Pushed, so an automated keeper mostly re-ships on illiquidity and recenters ranges.

Hosted APIs, MCP and paid access

Aqua's hosted/gated REST APIs, the MCP servers, x402 paid access, and private-mempool broadcast (Transaction Gateway) are part of 1inch Business (KYB/KYC-gated, payable). These docs cover the permissionless on-chain + SDK path only; broadcast the calldata you build here through your own RPC. For hosted infrastructure or agent tooling, see 1inch Business.

Read-only Aqua analytics are exposed to AI agents through the aqua tool on the 1inch MCP server: maker stats, strategy lists, and per-strategy state, activity, and volume series.

Honest caveat. The launch taker gate reads tx.origin, so agentic takers using smart accounts or 4337 bundlers cannot fill today. Agentic makers are unaffected — headless algo-LP works now. Computed metrics are estimates from public data, not official 1inch figures.

Did you find what you need?