Introducing Aqua — shared liquidity on the 1inch API, SDK, and MCP

Build on Aqua, the 1inch shared liquidity layer, across every surface — a read-only REST API for protocol analytics, the TypeScript SDK for on-chain ship/dock/pull/push, and an aqua tool on the 1inch MCP Server.

Aqua is now on 1inch Business. Aqua is a shared liquidity layer that lets liquidity providers allocate virtual token balances across multiple trading strategies — without fragmenting capital into isolated pools. This release brings every way to build on it into one place: a read-only REST API for protocol analytics, a TypeScript SDK for on-chain interactions, and an MCP Server tool for agentic access.

Ways to integrate

Pick the surface that fits your app — or combine them. All three share the same Aqua data model.

Aqua REST API

Query protocol state and on-chain analytics over HTTP: aggregated maker stats (TVL, fees, APY), a maker's strategies, per-strategy overview and token balances, on-chain activity (opens, closes, swaps), time-bucketed volume series, and a system-wide feed of currently open strategies across chains. All endpoints are read-only GETs and use your existing 1inch API key.

curl 'https://api.1inch.com/aqua/v1.0/strategies/opened?chainId=1&limit=100' \

-H 'accept: application/json' \

-H 'Authorization: Bearer YOUR_API_KEY'

Aqua TypeScript SDK

For on-chain interactions, the @1inch/aqua-sdk encodes and parses the protocol's core operations — ship and dock to allocate or remove virtual balances, and pull / push to move tokens during trade execution. Start from the Aqua app template for a working project scaffold.

import { AquaProtocolContract, AQUA_CONTRACT_ADDRESSES, Address, HexString, NetworkEnum } from "@1inch/aqua-sdk";

const aqua = new AquaProtocolContract(AQUA_CONTRACT_ADDRESSES[NetworkEnum.ETHEREUM]);

// Allocate virtual balances into a strategy

const shipTx = aqua.ship({

app: new Address("0x..."),

strategy: new HexString("0x..."),

amountsAndTokens: [{ token: new Address("0x..."), amount: 1000000000000000000n }]

});

1inch MCP Server

The 1inch MCP Server ships an aqua tool so your AI client can read Aqua analytics in place and preview, open and close maker positions. Analytics need no OAuth. Writes are non-custodial: your wallet signs every transaction. See how to manage Aqua positions from MCP.

Core concepts

Term	Meaning
`maker`	Liquidity provider who ships virtual balances into Aqua strategies.
`app`	Smart contract that implements a trading application on top of Aqua.
`strategy`	Immutable configuration that defines how virtual balances are used.
`ship / dock`	Lifecycle operations that allocate or remove virtual balances for a strategy.
`pull / push`	Swap-interface operations that move tokens during trade execution.

Supported chains

Aqua is available across 1inch's major EVM networks: Ethereum, BNB Chain, Polygon, Optimism, Arbitrum, Gnosis, Avalanche, zkSync, Base, Linea, Sonic, and Unichain.

Get started

Grab an API key in the 1inch Business portal (your existing key works across all Aqua surfaces).
Explore the endpoints in the Aqua API reference, or call them live in the API Playground.
For on-chain flows, install @1inch/aqua-sdk and clone the Aqua app template.
Point your AI client at the 1inch MCP Server to read Aqua analytics or manage maker positions with the aqua tool.