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: requireddeliver the output straight to an address you bind on the zap’srecipientport, not to the execution proxy. Today these are the IPOR deposits. - Composer API. A
lifi.zapnode 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.
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.

