What it does
LI.FI connects applications to token exchanges, bridges and solver routes. Developers can use its API, a connection for other software, its software toolkit or an embedded swap and bridge widget.
LI.FI is for teams adding token exchange to a wallet or application. A request identifies the starting asset and chain, the receiving asset and chain, and the wallet involved. LI.FI searches routes that can combine a swap with a bridge transfer, reducing the number of separate integrations a team must maintain.
Its end-to-end example follows the work beyond obtaining a price. A quote includes transaction data; an advanced routes response first requires choosing a route and requesting the data for that step. The application checks token spending permission, obtains approval when needed and submits the transaction on the source chain. A route with a second step needs the first step to finish before the application requests and submits the next transaction.
Status tracking deserves its own interface state. The status response distinguishes pending, failed and completed transfers, with additional outcomes such as partial delivery or a refund. Where a stored quote is available, compare the actual received amount with both the quoted estimate and minimum. A COMPLETED status does not promise that the received amount equals the original estimate, and a missing stored quote is not itself a failure.
The Standard plan is free to integrate; Enterprise has custom terms and higher limits. Transaction costs still apply to the routes used. Public routing endpoints permit access without an API key, while Earn and protected endpoints require one. Anonymous quotes and advanced route searches are each limited to 75 requests per two hours, making them more suitable for initial evaluation than a busy production interface.
The plans page advertises Standard capacity up to 200 requests per minute. Check the allocation in the Partner Portal and response headers before sizing an integration; the authentication guide gives newly created keys a default of 100 requests per minute, enforced across a rolling two hour window for quote related calls. Keep a key on the server. The browser widget does not need a key exposed in its configuration.
Strengths
- Combines exchange, bridge and solver routes through one integration
- Offers both developer tools and an embeddable swap interface
Watch out for
- Anonymous quote access has a much lower allowance than registered integrations
- Applications must handle pending, partial and refunded outcomes
Best for
- Wallet teams adding swaps across several chains
- Developers building transfer status and quote reconciliation into an application
Sources
- Universal Market Access for Digital Assets - LI.FI (Oct 27, 2026)
- LI.FI Plans (Oct 27, 2026)
- Rate Limits and API Authentication (Oct 27, 2026)
- End-to-end Transaction Example (Oct 27, 2026)
- Transaction Status Tracking (Oct 27, 2026)