APN cross-chain bridges for AI agents

Agent Payment Node (APN) moves value between chains through six routes: LI.FI with Across and Stargate, Relay, Circle CCTP V2, GasZip, NEAR 1Click and direct Stargate V2. Every route needs an owner allowlist admission on the bridge rail and a foreground approval. This page lists what each route covers and the commands to run.

Updated

Which bridges can an AI agent use with APN?

RouteWhat it movesCommands
LI.FI with Across V4 and Stargate V2 TaxiUSDC and ETH between Ethereum, Base and Arbitrum One, WBTC between Ethereum and Arbitrum One, plus Ethereum ETH to Linea, Monad and BNBbridge routes, bridge prepare, bridge approve
RelaySeven pinned routes, such as Ethereum USDC to Base ETH and Base ETH to Polygon POLrelay prepare, execute, observe, status, retire
Circle CCTP V2 FastUSDC from Arbitrum One to Sei, Linea or Monadcircle evm *
Circle CCTP V2, Base to SolanaBase USDC to Solana USDCcircle source submit, circle approval *
GasZipBase ETH to the owner's own Sei SEI or Mega ETHsei funding *, mega funding *
NEAR 1ClickBase USDC or Ethereum ETH to TRON or Solanaoneclick source submit
Direct Stargate V2Ethereum ETH to Unichain ETH; Optimism USDC to Polygon USDCstargate native *, stargate token *

Only the local EVM wallet profile can bridge. Coinbase Agentic Wallet, MetaMask Agent Wallet and MetaMask Smart Account have no bridge execution and recovery contract, and no profile silently falls back to the local signer. See wallets. A chain or tool that a provider lists does not make it executable in APN.

Which owner allowlist rail applies to bridges?

The bridge rail. The owner admits the exact source asset on bridge with per-operation and daily caps and the exact mechanism. Prepare checks the policy, and approval reserves the amount in the shared UTC-day usage ledger before signing. A changed policy refuses with allowlist_policy_changed. A recipients pin on the destination chain is optional. See security.

RouteMechanism { provider, reference }
LI.FI Across V4lifi, across-v4
LI.FI Stargate V2 Taxilifi, stargate-v2-taxi
Relayrelay, one reference per route, for example ethereum-usdc-base-eth-v1
Circle CCTP V2 Fastcircle-cctp-v2, circle-v2-evm-fast-42161-<destination>.v2
GasZip to Seigaszip, v2-direct-base-sei-self-0100f6.1
GasZip to Megagaszip, v2-direct-base-mega-self-010202.1
NEAR 1Clicknear-1click, <lane>.v1
Stargate V2 nativestargate-v2, eip155:1:0x77b2043768d28E9C9aB44E1aBfC95944bcE57931/eip155:130:0xe9aBA835f813ca05E50A6C0ce65D0D74390F7dE7

An admission can also list 2 to 16 alternative mechanisms, each with its own cap.

How does an agent bridge USDC with LI.FI?

Ethereum, Base and Arbitrum One are source chains. BNB Smart Chain, Monad and Linea are destinations only, reached from Ethereum with native ETH to the owner's own address. USDC works between Ethereum, Base and Arbitrum One over Across and Stargate pool 1. Ethereum ETH to Base ETH also runs over Stargate. Every option is required and has no default.

apn bridge capabilities
apn bridge routes --profile existing-local \
  --from-chain eip155:1 --to-chain eip155:8453 \
  --from-token 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 \
  --to-token 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 \
  --amount 10 --to <recipient> --min-output 9.9 \
  --max-native-debit-wei 20000000000000000 \
  --max-route-fee 0.1 --slippage-bps 50

apn bridge prepare --profile existing-local \
  --quote <quote-hash> --route <returned-route-id> \
  --idempotency-key bridge-example-001

apn bridge approve --operation <operation-id>
  • routes lists every route LI.FI returns, either preparable or with its gate. Prepare validates the complete call before creating the durable operation.
  • Only a zero allowance or an exact existing allowance to the LI.FI Diamond is accepted. APN never resets, increases or revokes an allowance on its own.
  • Frozen EIP-1559 prices carry a 50% headroom (5000 basis points). --max-native-debit-wei is checked against that worst case, not the quote.
  • Quote materialization lasts at most 300 seconds, and at least 15 seconds must remain before each first send.
  • Ethereum USDT and WETH have no admitted route. Solana and TRON bridge directions through LI.FI are not executable.

Configure each chain with its APN_<CHAIN>_RPC_URL variable. There is no default endpoint for bridge commands, and the generic --rpc-url is not a fallback.

Which Relay routes does APN support?

Source--assetDestination
EthereumusdcBNB native, or Base ETH
BNBnativePolygon POL, or Monad MON
BasenativeMegaETH USDm, or Polygon POL
Arbitrum OneusdcEthereum USDC
apn relay prepare --profile <profile> --source-chain <caip2> --asset <usdc|native> --destination-chain <caip2> --recipient <address> \
  --amount-atomic <source-atomic> --min-output-atomic <destination-atomic> --max-deposit-network-fee-wei <wei> \
  [--max-approval-network-fee-wei <wei>] [--payer <address> --max-provider-fee-atomic <usdc> --quote-file <absolute-json-path>] \
  --idempotency-key <key>
apn relay execute --profile <profile> --operation <operation-id> --rpc-url <source-rpc>
apn relay observe --profile <profile> --operation <operation-id> --rpc-url <source-rpc> [--destination-rpc-url <destination-rpc>]

Relay is not exposed as MCP tools. A route-only option is required on its route and refused on others. Any other combination is refused with relay_route_unknown.

How does Circle CCTP V2 move USDC?

apn circle evm moves USDC from Arbitrum One to Sei, Linea or Monad with CCTP V2 Fast. A source wallet approves and burns USDC on Arbitrum. A destination wallet submits the mint and pays its gas. The minted USDC goes to a beneficiary you name.

apn circle evm prepare --profile <source-profile> --destination-profile <gas-profile> \
  --destination-chain <1329|59144|143> --idempotency-key <key> --beneficiary <address> \
  --gross-atomic <amount> --max-issuer-fee-atomic <cap> --min-mint-atomic <floor>
apn circle evm approve-source --operation <operation-id>
apn circle evm observe --operation <operation-id>
apn circle evm approve-mint --operation <operation-id>

Source signing expires 15 minutes after preparation. Base USDC to Solana USDC runs through apn circle source submit. APN only reads the Solana delivery and never signs on Solana for it.

What are the GasZip, NEAR 1Click and direct Stargate lanes?

  • GasZip funds the profile's own Sei or Mega account with Base ETH. Payer and recipient are the same address, and no token approval is involved.
  • NEAR 1Click sends one deposit on a pinned lane: base-usdc-to-tron-usdt, ethereum-eth-to-tron-trx, ethereum-eth-to-solana-sol and ethereum-eth-to-tron-usdt. One deposit is at most 10,000,000 USDC on the Base lane and 1 ETH on the Ethereum lanes.
  • Direct Stargate V2 has two lanes, both self-only: Ethereum ETH to Unichain ETH, and Optimism USDC to Polygon USDC with an optional POL native drop.
apn sei funding prepare --profile <profile> --expected-payer <profile-wallet-address> --amount-atomic 10000000000000 --minimum-output-atomic 250000000000000000 --maximum-fee-atomic 1000000000000 --idempotency-key <new-key>
apn sei funding approve --operation <operation-id>

apn oneclick source submit --lane ethereum-eth-to-tron-trx --profile <profile> --expected-payer <ethereum-payer> \
  --recipient <tron-recipient> --amount-atomic 2000000000000000 --min-output-atomic 12500000 \
  --max-quoted-loss-atomic 200000 --max-gas-limit-atomic 60000 --max-fee-per-gas-wei 20000000000 \
  --max-priority-fee-per-gas-wei 2000000000 --max-native-debit-wei 2600000000000000 --idempotency-key trx-fund-1
apn oneclick source status --operation <operation-id>

apn stargate native prepare --profile <profile> --amount-atomic <wei> --max-native-debit-atomic <wei> --idempotency-key <key>
apn stargate native execute --operation <operation-id>

The Stargate quote is read-only and never admits execution by itself. For the Optimism to Polygon lane, use apn stargate token prepare and execute. The Stargate source registry lists 13 rows, but only these two lanes execute.

What happens if a bridge fails midway?

Every effect needs foreground consent in a terminal. Recovery observes. It never signs a replacement or resends. See recovery.

  • operation status, operation resume and receipt get handle durable bridge operations. Over MCP, apn_bridge_routes and apn_bridge_prepare run directly, and apn_foreground_handoff returns the approval command.
  • A destination is proven independently. For GasZip, the provider's status alone cannot complete the operation.
  • An unsent LI.FI operation past its quote expiry ends as failed_before_effect, or failed_after_approval after a safe approval.
  • A signed 1Click source that can never land ends failed_proven_superseded through status.

Questions

Can an AI agent bridge funds with LI.FI through APN?

Yes, from the local wallet, between Ethereum, Base and Arbitrum One for USDC, and from Ethereum ETH to Linea, Monad and BNB. LI.FI is limited to its Across V4 and Stargate V2 Taxi tools.

Which APN bridge reaches Solana or TRON?

NEAR 1Click sends Base USDC or Ethereum ETH to TRON and Solana. Circle CCTP V2 sends Base USDC to Solana USDC. LI.FI Solana and TRON directions are not executable.

Do APN bridge commands have a default RPC?

No. Each chain needs its APN_<CHAIN>_RPC_URL variable, and the generic --rpc-url is not a fallback.

Can a human-free agent approve a bridge?

No. Every bridge effect needs a foreground terminal approval. MCP returns only the command.

Sources
  1. lifi.md: LI.FI, GasZip, NEAR 1Click, Circle to Solana
  2. relay.md: Relay routes
  3. circle-v2-evm-fast.md: CCTP V2 Fast
  4. stargate-v2-direct-quote.md: Stargate registry
  5. stargate-v2-native-execution.md: ETH to Unichain
  6. stargate-v2-token-native-drop.md: USDC Optimism to Polygon
  7. allowlist-policy.md: bridge rail