LI.FI

• Name: LI.FI
• URL: https://li.fi/
• Tags: ethereum-ecosystem solana-ecosystem
• Category: Cross-chain routing and execution infrastructure / bridge and DEX aggregation
• Summary: LI.FI is route-orchestration middleware. The useful read is not one API to everything; it is a venue-admission and route-ranking layer that lets wallets and apps outsource multichain execution defaults across bridges, DEXs, solvers, and widgets.
• What it does:
  • Aggregates bridge, exchange, and solver liquidity across multiple blockchain ecosystems behind one integration surface
  • Provides REST APIs, SDKs, and embeddable widgets for swap, bridge, and cross-chain execution flows
  • Calculates routes based on factors such as price, gas cost, speed, and execution reliability
  • Supports multi-step flows including bridge-plus-swap, bridge-plus-deposit, and other cross-chain contract-call patterns
  • Exposes AI-agent-oriented documentation, machine-readable docs, and related tooling for agentic integrations
• Key claims:
  • Docs describe LI.FI as a “routing and orchestration layer” connecting applications to onchain liquidity across chains, bridges, DEXs, solvers, and yield protocols through a single integration
  • Official docs say developers can use one integration for same-chain swaps, cross-chain swaps and bridging, cross-chain contract calls, and multi-step DeFi workflows
  • API docs state the public base URL is https://li.quest/v1 and that most API use cases can be covered with quote, status, chains, tokens, and tools endpoints
  • Agent docs say LI.FI supports 58 blockchains and aggregates 27 bridges plus 31 exchanges in the current documentation pass
  • The GitHub organization and docs show an active product surface spanning SDK, widget, contracts, token lists, and related developer tooling
• Whitepaper: No classic whitepaper or litepaper was found during this pass. Primary-source snapshots were saved in ../whitepapers/li-fi-primary-sources-2026-04-22.md.
• Sources:
  • https://li.fi/
  • https://li.fi/how-it-works/
  • https://docs.li.fi/introduction/introduction.md
  • https://docs.li.fi/api-reference/introduction
  • https://docs.li.fi/sdk/overview
  • https://docs.li.fi/agents/overview
  • https://github.com/lifinance

Internal linkages

• Best upward reads for route orchestration and hidden-defaults control planes: across and skip.
• Keep this note on route ranking, venue admission, fallback policy, and integrator defaults rather than pretending LI.FI is peer to every bridge or intent system it can touch.

Control surface

• Authority sits in venue admission, route ranking, fee insertion, fallback behavior, widget defaults, and which same-chain, cross-chain, or contract-call paths LI.FI keeps first-class.

• The important read is not that LI.FI can touch many bridges. It is that wallets and apps can let LI.FI decide which bridge, DEX, or solver gets the order and how much execution truth comes back through its own APIs.

• Treat it as route-orchestration middleware, not as a neutral interoperability base layer.

• Last reviewed: 2026-06-14 UTC