Skip to main content
Use the live catalog below to find every protocol Composer routes into (vaults, lending markets, staking tokens, wrappers and mint/burn pairs), with its chains, token addresses, edge types, deposit limits and recipient requirements. The catalog applies to both the Composer API and the LI.FI API, with one exception: IPOR vaults are available only through the Composer API. The view has two parts: Supported protocols, one row per protocol with the chains it covers, and Routing edges, a searchable table of every edge. A vault usually appears twice, once to enter and once to exit.

How routing edges work

A routing edge turns one token into another on one chain through one protocol action, for example USDC → aEthUSDC through an Aave v3 deposit. Each edge has one of six types: enter-position, exit-position, wrap, unwrap, mint or burn. For the LI.FI API, enter-position means deposits are supported and exit-position means withdrawals are supported; use the edge’s output token address as toToken.
  • Deposit limits. Some edges carry inAmountMin / inAmountMax, in the input token’s base units. The protocol rejects an amount outside them.
  • Recipient. Edges marked recipient: required deliver the output straight to an address you bind on the zap’s recipient port, not to the execution proxy. Today these are the IPOR deposits.
  • Composer API. A lifi.zap node uses exactly one edge, matched on its input and output token, and never adds a swap. sdk.route (POST /compose/route) chains up to two hops, with a swap allowed only as the first hop; see Deposit with a server-planned route.
The table is fetched live from GET https://composer.li.quest/compose/zap-packs, and chain names from GET https://composer.li.quest/chains. Testnet edges are included. For the chains that serve cross-chain flows, see Availability.

Requesting a new protocol integration

To get a protocol integrated, see New Protocol Onboarding.