Flow. Each op has input ports, output ports and a config schema. The SDK exposes every op as a typed method on the flow builder: lifi.swap is builder.lifi.swap(...). IDE autocomplete on @lifi/composer-sdk shows each op’s port names and config types. To wire ops together, see Build a same-chain flow.
Choose an op
Same-chain
Cross-chain
The Uniswap deposit ops call the router with zero minimums. Protect them with a
band guard on the pool price port (poolPrice or sqrtPriceX96) and a slippage guard on liquidity.
Future outputs
A future output lands after the transaction that starts it has settled, usually on another chain. Three ops have one:lifi.bridge.amountOut, lifiIntents.order.amountOut and continuation.settle.output. A future output:
- Can’t feed another op in the same flow. The exception: a
lifi.bridgeorlifiIntents.orderoutput can fund acontinuation.settlenode, which starts a cross-chain flow. See Cross-chain flows. - Takes no guards. Its
amount.minimumis the minimum the bridge or the Intents solver committed to. - Reports how it arrives. Its
deliveryis{ when: 'future', etaSeconds?, provider?, trackingId? }. Seelifi.bridgetracking.
Live catalog
The table below is read fromGET https://composer.li.quest/compose/manifest when the page loads. It omits internal ops that you never write.

