LI.FI

This is a reference for the verification API’s payload adapter. For apps you can use inside a Desk, see Desk apps.

venue: lifi. Over HTTP, liquest, jumper and lifiprotocol also resolve to it.

What to send

All three shapes are detected without venue. All are in the swap family.

`actionType`	Payload
`quote-request`	The `GET /v1/quote` parameters: `{fromChain, toChain, fromToken, toToken, fromAmount, fromAddress, toAddress?, slippage?, fee?, ...}`
`routes-request`	The `POST /v1/advanced/routes` body: `{fromChainId, toChainId, fromTokenAddress, toTokenAddress, fromAmount, fromAddress, options?}`
`route`	A quote or step LI.FI returned (`{action, estimate, tool, transactionRequest}`), or a route object with `steps`

The summary decodes amounts from their decimals-scaled form, names the chains, and for a route shows the tool, the estimated output and the claimed minimum (toAmountMin). The attached transactionRequest calldata is not decoded.

Live re-quote

The adapter asks LI.FI for a fresh quote for the same trade, GET https://li.quest/v1/quote, with the payload’s chains, tokens, amount, fromAddress and slippage. It adds the tool LI.FI would use now, the fresh estimate, the guaranteed minimum and their dollar values. For a route payload it compares the claimed toAmountMin with the fresh minimum:

More than 2% above the fresh minimum: the route’s numbers are stale or overstated.
More than 5% below: the route accepts that much more loss than the market needs.

The re-quote needs fromAddress, which LI.FI requires. Without it, or when LI.FI returns no route, times out (7 seconds) or rate-limits the request, a note says the amounts are unverified and tells the judge to lean ESCALATE when your rules depend on the output. Results are cached for 60 seconds.

Notes the classifier adds

slippage is a fraction: 0.005 is 0.5%. Values above 0.01 are flagged, and values above 0.5 are outside LI.FI’s accepted range.
Amounts are integers in the token’s smallest unit. The classifier knows the decimals of USDC, USDT, DAI, WETH, ETH and WBTC, and of any token object that states them. Other tokens are shown raw until the re-quote names them.
A toAddress different from fromAddress sends the entire output to another wallet.
An integrator fee, fromAmountForGas, a maxPriceImpact above 10%, and a route with no toAmountMin.

Example

const action = {
  fromChain: 42161, // Arbitrum
  toChain: 8453, // Base
  fromToken: "USDC",
  toToken: "USDC",
  fromAmount: "2500000000", // 2,500 USDC, 6 decimals
  fromAddress: "0x552008c0f6870c2f77e5cC1d2eb9bdff03e30Ea0",
  slippage: 0.005,
};

const res = await fetch("https://harness.chance.cc/api/v1/intent", {
  method: "POST",
  headers: { "x-api-key": process.env.CHANCE_API_KEY!, "Content-Type": "application/json" },
  body: JSON.stringify({
    intent: "Treasury rebalancing only: USDC to USDC, Arbitrum to Base, max 0.5% slippage, funds stay in the treasury wallet.",
    venue: "lifi",
    action,
  }),
});
const result = await res.json();
if (result.verdict !== "ALLOW") throw new Error(result.reasoning ?? result.error);
// Only now request the quote from li.quest and submit its transaction.

From an MCP client

Instruct the agent to call verify_intent before executing any LI.FI route, with your rules as intent, the exact request or route as action and venue: "lifi", and to act only on ALLOW.

Integrate

Chance verification

Payload adapters

HTTP endpoints

What to send

Live re-quote

Notes the classifier adds

Example

From an MCP client

​What to send

​Live re-quote

​Notes the classifier adds

​Example

​From an MCP client

What to send

Live re-quote

Notes the classifier adds

Example

From an MCP client