LI.FI
LI.FI is the routing and execution layer for cross-chain liquidity, payments, swaps and yield. A single integration gives an application access to more than 100 aggregated bridges, DEXs, DEX aggregators and intent-based solvers across 58+ chains spanning EVM, Solana, Bitcoin, SUI and TRON. The LI.FI API returns an optimal route plus a ready-to-sign, unsigned transaction; the product set extends to Composer for one-click DeFi deposits across 20+ protocols, Earn for yield discovery and portfolio tracking, an intent/solver marketplace built on the Open Intents Framework, an embeddable Widget, a TypeScript SDK, a CLI and a hosted MCP server for AI agents.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles LI.FI the way a machine reads it — 24 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — LI.FI scores 57.4/100 (developing), with a separate agent-readiness read of 76/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile LI.FI
Each block below is one kind of artifact we hold for LI.FI. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
LI.FI Intents Order Server API
Intent-based execution API for the LI.FI solver marketplace. Integrators request quotes and submit orders; solvers publish standing quote inventory and fill intents. Built on th...
LI.FI advanced API
The advanced API from LI.FI — 3 operation(s) for advanced.
LI.FI Analytics API
The Analytics API from LI.FI — 4 operation(s) for analytics.
LI.FI Calldata API
The Calldata API from LI.FI — 1 operation(s) for calldata.
LI.FI Chains API
The Chains API from LI.FI — 1 operation(s) for chains.
LI.FI Connections API
The Connections API from LI.FI — 1 operation(s) for connections.
LI.FI Earn Chains API
The Earn Chains API from LI.FI — 1 operation(s) for earn chains.
LI.FI Earn Portfolio API
The Earn Portfolio API from LI.FI — 1 operation(s) for earn portfolio.
LI.FI Earn Protocols API
The Earn Protocols API from LI.FI — 1 operation(s) for earn protocols.
LI.FI Earn Vaults API
The Earn Vaults API from LI.FI — 2 operation(s) for earn vaults.
LI.FI Gas API
The Gas API from LI.FI — 5 operation(s) for gas.
LI.FI Integrators API
The Integrators API from LI.FI — 2 operation(s) for integrators.
LI.FI Quote API
The Quote API from LI.FI — 4 operation(s) for quote.
LI.FI Relayer API
The Relayer API from LI.FI — 3 operation(s) for relayer.
LI.FI Status API
The Status API from LI.FI — 1 operation(s) for status.
LI.FI Token API
The Token API from LI.FI — 1 operation(s) for token.
LI.FI Tokens API
The Tokens API from LI.FI — 1 operation(s) for tokens.
LI.FI Tools API
The Tools API from LI.FI — 1 operation(s) for tools.
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
lifi-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Lifi Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for LI.FI — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lifi · machine-readable index on apis.io