toToken to a supported protocol’s position-token address, and the routing engine adds a Composer route to the candidates it compares.
How Composer is selected
Composer is one of the tools the LI.FI routing engine compares, alongside DEX aggregators and bridges. When a DEX can buy the vault token directly at a better rate, the engine returns that DEX route instead, and the user still receives the vault token. To tell whether a quote uses Composer, check its steps: a Composer route has at least one entry inincludedSteps with tool: "composer". Do not rely on the top-level tool: in a cross-chain route it names the bridge (for example across), even when Composer runs the deposit on the destination chain. See Identifying Composer routes.
Try it out
Request a quote to deposit 1 USDC into the Spark-curated Morpho USDC vault on Base:Run your first Composer transaction
Execute your first Composer transaction step by step.
Choose your integration path
API
Direct REST API integration for full control over the Composer flow.
SDK
Use the LI.FI TypeScript SDK for managed execution, status tracking, and
error handling.
Widget
Drop-in UI component. Composer works without extra code.
Current limitations
- Supported EVM chains only. Composer runs on the EVM chains listed in Supported Protocols & Chains. Solana and other non-EVM chains are not supported.
- Tokenised positions only. Composer targets must return a token (e.g., vault tokens, LP tokens, LSTs). Some protocols support deposits only, not withdrawals.
- Predefined routes only. Through the LI.FI API, Composer runs a deposit or withdrawal of at most two hops, optionally after a bridge. Custom multi-step flows and cross-chain flows are available only through the Composer API.
Security
For contract audits, the bug bounty and monitoring, see Security and Audits.Next steps
Recipes
Deposit examples for vault, staking and lending protocols
Cross-chain deposits
Bridge and deposit across EVM chains
Withdrawals
Withdraw from protocol positions

