Agent skill · software engineering · aiskillstore
lifi
Use the LI.FI REST API for cross-chain and same-chain token swaps, bridging, DeFi deposits through Composer, yield discovery and position tracking through Earn, and solver-based Intents. Use to find routes or quotes, move assets between chains, execute same-chain swaps, deposit into vaults or lending and staking protocols, inspect APY and TVL, run gasless or optimized stablecoin transfers, build multi-chain payments, query supported chains, tokens, bridges, and gas prices, track or recover transactions, inspect transfer history and analytics, withdraw integrator fees, or add cross-chain functionality to apps, backends, bots, and AI agents.
Why this skill is useful
Adds executable scripts for cross-chain token swaps and DeFi interactions that are not covered in public documentation.
What it needs
Requires curl installed locally. Requires li.fi account access. About 10k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
LI.FI API Integration LI.FI aggregates bridges, DEXs, intent solvers, and DeFi protocols behind one API. This skill covers the full product surface: Product Base URL What it does --------- ---------- -------------- Core API (swaps & bridges) https://li.quest/v1 Quotes, routes, execution data, status tracking across 75+ chains Composer (DeFi execution) https://li.quest/v1 (same /quote endpoint) One-click swap/bridge + deposit/withdraw into vaults, lending, staking Earn (yield data) https://earn.li.fi/v1 Vault discovery, APY/TVL analytics, portfolio positions Intents (solver marketplace) https://order.li.fi Intent-based orders filled by a competitive solver network For AI agents, LI.FI also offers an MCP server (https://mcp.li.quest/mcp) and a CLI (@lifi/cli). LI.FI recommends agents and backends use the REST API directly rather than the SDK. Authentication & Rate Limits API key is optional — it only raises rate limits. Header: x-lifi-api-key (get one at the LI.FI Partner Portal). Tier /quote, /advanced/routes /advanced/stepTransaction Other endpoints ------ ------------------------------ ------------------------------ ----------------- Without API key 75 req / 2 hours 50 req / 2 hours 100 req / minute With API key (default) 100 RPM (2-hour rolling window: 12,000 / 2h) same 100 RPM Responses include ratelimit-limit, ratelimit-remaining, ratelimit-reset (seconds) headers. 429 responses carry error code 1005. Never expose your API key in client-side code. Quick Start — The Five-Call Recipe The canonical flow for any swap/bridge: From the quote response, extract: transactionRequest (sign & send), estimate.approvalAddress (ERC-20 spender), estimate.toAmount/toAmountMin, estimate.executionDuration (basis for polling), and tool (pass as bridge to /status). Quotes go stale in ~60 seconds — re-fetch before signing if older (and always after a separate approval tx). Core Endpoints GET /quote Single best route with transaction data ready for execution. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/lifi