Skip to main content
This guide covers the requirements a protocol must meet to be integrated with LI.FI Composer and how onboarding works. For what Composer is, see the Composer overview.

What integration gives you

LI.FI is integrated into hundreds of wallets, dApps and DeFi platforms. Once your protocol is integrated, their users can deposit into it directly, without opening your UI. Your position token becomes a valid destination for Composer routes, reachable from supported tokens on any Composer-supported EVM chain through:
  • LI.FI API, SDK and Widget: your vault or staking token appears as a valid toToken destination
  • Composer API: developers can use your protocol as a step in their own flows, including cross-chain flows that deposit on the destination chain after a bridge
Composer also shortens the path to a deposit: Every Composer route is simulated before it is returned for signing, and routes that would revert at that point are dropped.

Technical requirements

1. EVM compatibility

Your protocol must be deployed on a chain listed in Supported Protocols & Chains. Non-EVM chains (Solana, Sui, etc.) are not supported.

2. Tokenised position return

On deposit, your protocol must return an ERC-20 token to the user’s wallet that represents the position. Integrators request Composer routes by setting toToken to that token. Supported token types: Protocols that return no token on deposit are not supported.

3. Standard deposit interface

Your deposit function must accept the deposit amount as a parameter, and a recipient where the function has one, because the amount comes from the output of the preceding swap or bridge step at execution time. Common patterns:
  • ERC-4626 deposit(uint256 assets, address receiver): standard vault interface
  • Aave-style supply(address asset, uint256 amount, address onBehalfOf, uint16 referralCode): lending pool interface
  • Staking stake(uint256 amount) or wrap(uint256 amount): staking/wrapping interface
LI.FI confirms compatibility during onboarding.

Deposit vs. withdraw support

Some protocols are integrated with deposit only (e.g., Kinetiq, Ethena, Maple); withdraw support can be added later. The Supported Protocols & Chains table shows which protocols support each action.

After integration

Users reach your protocol with a standard quote:
Three factors affect what users see:
  • Route competition. Composer competes with DEX routes into the same token. If a DEX sells your vault token more cheaply, the LI.FI API returns that route.
  • Permissioned products. Products that require authorization need LI.FI to integrate the issuer’s authorization service first. See Permissioned Products & Compliance.
  • Custody constraints. Positions that the LI.FI contracts cannot hold during a route are available only through the Composer API. See Limitations.

Getting integrated

The LI.FI team handles integrations and works with you directly.

Apply for Composer Integration

Fill out the protocol integration form to start the process.
You can also reach out directly: