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.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles LI.FI the way a machine reads it — 42 machine-readable artifacts across 2 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 55.5/100 (strong), with a separate agent-readiness read of 40/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from LI.FI's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lifi/"
title="LI.FI on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lifi.svg"
alt="LI.FI Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/lifi/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lifi/"
title="LI.FI on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lifi/card.svg"
alt="LI.FI Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 ·
Open Collections 18
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONLI.FI Earn advanced API
OPEN COLLECTIONLI.FI Earn advanced Analytics API
OPEN COLLECTIONLI.FI Earn advanced Calldata API
OPEN COLLECTIONLI.FI Earn advanced Chains API
OPEN COLLECTIONLI.FI Earn advanced Connections API
OPEN COLLECTIONLI.FI Earn advanced Earn Chains API
OPEN COLLECTIONLI.FI Earn advanced Earn Portfolio API
OPEN COLLECTIONLI.FI Earn advanced Earn Protocols API
OPEN COLLECTIONLI.FI Earn advanced Earn Vaults API
OPEN COLLECTIONLI.FI Earn advanced Gas API
OPEN COLLECTIONLI.FI Earn advanced Integrators API
OPEN COLLECTIONLI.FI Earn advanced Quote API
OPEN COLLECTIONLI.FI Earn advanced Relayer API
OPEN COLLECTIONLI.FI Earn advanced Status API
OPEN COLLECTIONLI.FI Earn advanced Token API
OPEN COLLECTIONLI.FI Earn advanced Tokens API
OPEN COLLECTIONLI.FI Earn advanced Tools API
OPEN COLLECTIONScroll 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.
LI.FI MCP Server
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
This is an independent, third-party profile of LI.FI, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.