How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
LI.FI

LI.FI Relayer API

The Relayer API from LI.FI — 3 operation(s) for relayer.

Documentation Provider Profile APIs.io OpenAPI GitHub

LI.FI Relayer API is one of 18 APIs that LI.FI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Relayer. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 3 paths, and defines 33 schemas. It is described by OpenAPI 3.0.0, at version 0.1.0.

Requests are made against a single base URL, https://earn.li.fi.

3 operations 3 paths 33 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
0.1.0
Base URL
https://li.quest
Authentication
API Key
Resource Areas
1

Authentication & Security 1

LI.FI Relayer API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-lifi-api-key (x-lifi-api-key). By default, every request must be authenticated.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Relayer 3
GET
/v1/relayer/status/{taskId}
Cross chain relay transfers might take a while to complete. Waiting on the transaction on the sending chain doesn't help here. For this reason we build a simple endpoint that let's you check the stat…
→ 200
GET
/v1/relayer/quote
Get a quote for a relayed token transfer
25 params → 200400404
POST
/v1/relayer/relay
Send a signed permit2 transaction to be dispatched by a transaction relayer
body → 200

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are ContractTransactionSchema (15 properties), TransactionInfo (13 properties), StatusResponse (12 properties), Step (11 properties). Each schema is shown below with its type and property counts.

RelayWithnessType
object
1 property
RelayQuoteData
object
2 properties
RelayRequestSchema
object
5 properties 3 required
QuoteExchangesEnum
string
Exchange tool identifier or keyword. Retrieve current exchange keys from the /v1/tools endpoint. Supported keywords: all, none, default, [].
RelayTransactionStatusResponse
object
2 properties 1 required
RelayAccessList
object
2 properties
Token
object
Representation of a Token
8 properties 5 required
IncludedSwapSteps
object
The included steps contain tool name and details, sending and receiving token data and amounts.
7 properties
Metadata
object
The metadata of the transaction which includes integrator data, etc.
1 property
QuoteBridgesEnum
string
Bridge tool identifier or keyword. Retrieve current bridge keys from the /v1/tools endpoint. Supported keywords: all, none, default, [].
RelayResponse
object
2 properties
Estimate
object
An estimate for the current transfer
11 properties 6 required
RelayWitness
object
2 properties
UnavailableRoutes
object
2 properties
RelayQuote
object
6 properties
PermittedTokenSchema
object
2 properties
ToolError
object
Describes why a certain operation (like a quote request) failed.
5 properties
IncludedStep
object
Object that represents one step of an IncludedSteps array in Route
6 properties 6 required
RelayTransactionMetadata
object
Extra information about a relay transaction
2 properties
GasCost
object
Gas costs included in the transfer
7 properties 3 required
RelayPermitSchema
object
A set of parameters specifying the token, permitted amount, spender address, nonce (for uniqueness), and deadline (for expiration) in a Permit2 allowance grant.
4 properties 4 required
RelayTransactionStatus
object
Status details of a relay transaction
4 properties
ContractTransactionSchema
object
15 properties
TransactionInfo
object
A transaction info object
13 properties 5 required
StatusResponse
object
The current status of a transfer
12 properties 3 required
Action
object
Object describing what happens in a Step
8 properties 5 required
Step
object
Object that represents one step of a Route
11 properties 4 required
RelayQuoteResponse
object
2 properties
RelayPermitWithWitness
object
5 properties
RelayWitnessFull
object
3 properties
RelayResponseData
object
1 property
RelayWitnessParameters
object
2 properties
FeeCost
object
Fees included in the transfer
7 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lifi-relayer-api-openapi.yml Raw ↑

Other APIs LI.FI publishes across the network.

LI.FI Intents Order Server API
AE Profile APIs.io
LI.FI advanced API
AE Profile APIs.io
LI.FI Analytics API
AE Profile APIs.io
LI.FI Calldata API
AE Profile APIs.io
LI.FI Chains API
AE Profile APIs.io
LI.FI Connections API
AE Profile APIs.io
LI.FI Earn Chains API
AE Profile APIs.io
LI.FI Earn Portfolio API
AE Profile APIs.io
LI.FI Earn Protocols API
AE Profile APIs.io
LI.FI Earn Vaults API
AE Profile APIs.io
LI.FI Gas API
AE Profile APIs.io
LI.FI Integrators API
AE Profile APIs.io
#Relayer
← Back to L APIs
API Details
ID
lifi:lifi-relayer-api
Base URL
https://li.quest
Docs
https://docs.li.fi/api-reference/introduction
Provider
LI.FI
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=lifi-relayer-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lifi-relayer-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of LI.FI Relayer API, 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.