Abstraxn Agent Kit supports LiFi cross-chain and same-chain swaps using your integrator name, API key, and integrator fee (BYOK). Agents call the lifi_swap_quote MCP tool; your backend signs approval and route transactions with the agent wallet accessKey.

​
Supported chains

ethereum, base, polygon, arbitrum-one, bsc Same-chain swaps use one network slug. Cross-chain routes set chain (source) and to_chain (destination).

​
Dashboard setup

  1. Open Agentic Stack → Integrations for your application.
  2. Enable LiFi and enter:
    • Integrator name — from the LiFi partner portal
    • API key — for higher rate limits (x-lifi-api-key)
    • Integrator fee — decimal fraction (e.g. 0.005 = 0.5%)
  3. Save — credentials are encrypted server-side and included in agent validation for MCP calls.
LiFi credentials are stored per application, not per end user. All agents under that app share the integration when enabled.

​
MCP tool: lifi_swap_quote

The tool returns an unsigned approval transaction (if needed) and an unsigned route transaction for the agent EVM wallet on the source chain.

​
LiFi specialist chat

In the sample web app, open chat with ?serviceAgent=lifi (or pick the LiFi category). The backend:
  • Filters tools to LiFi-relevant MCP calls
  • Injects LiFi-specific system prompts
  • Routes swap and bridge requests to lifi_swap_quote (not Uniswap or evm_swap_quote)

​
Execution modes

See Swap confirmation for the confirmation UI and API.

​
Transaction history

Confirmed routes are recorded as chat_lifi_swap (and approvals as chat_lifi_approval) in agent transaction history.

Third-party integrations

BYOK overview, architecture, and deployment.

Swap confirmation

Confirm / cancel UX and REST endpoints.

MCP tools reference

Full tool catalog including lifi_swap_quote.

Uniswap integration

Same-chain Uniswap swaps via uniswap_swap_quote.