APN direct transfers on EVM networks

Agent Payment Node (APN) lets an AI agent send native coins and listed tokens, such as USDC on Base, from a local wallet on eleven EVM mainnets. The agent prepares the transfer. A human owner approves it in a terminal. This page lists the exact networks and assets, the commands, and what happens when something fails.

Updated

Which EVM networks and tokens can an AI agent send with APN?

A local encrypted wallet can read balances and send direct transfers of native coins and listed tokens on eleven EVM mainnets. Every transfer follows the same prepare, approve and recover flow. The owner allowlist policy caps it, and it uses an RPC endpoint the caller names explicitly.

NetworkCAIP-2NativeTokens (pinned contract)Completion
Ethereumeip155:1ETHUSDC 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48, USDT 0xdAC17F958D2ee523a2206206994597C13D831ec7, WETH 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2inclusion
Baseeip155:8453ETHUSDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, WETH 0x4200000000000000000000000000000000000006inclusion
Arbitrum Oneeip155:42161ETHUSDC 0xaf88d065e77c8cC2239327C5EDb3A432268e5831, USD₮0 0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9safe head
OP Mainneteip155:10ETHUSDC 0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85inclusion
Polygon PoSeip155:137POLUSDC 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359inclusion
BNB Smart Chaineip155:56BNBnone (native only)safe head
Avalanche C-Chaineip155:43114AVAXUSDC 0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E, USDT 0x9702230A8Ea53601f5cD2dc00fDBc13d4dF4A8c7safe head
Unichaineip155:130ETHUSDC 0x078D782b760474a361dDA0AF3839290b0EF57AD6inclusion
Lineaeip155:59144ETHUSDC 0x176211869cA2b568f2A7D4EE941E073a821EE1ffinclusion
Monadeip155:143MONUSDC 0x754704Bc059F8C67012fEd69BC8A327a5aafb603safe head
Sei EVMeip155:1329SEIUSDC 0xe15fC38F6D8c56aF07bbCBe3BAf5708A2Bf42392safe head

Native coins have 18 decimals. USDC, USDT and USD₮0 have 6. WETH has 18.

  • Direct transfers accept only these assets. Any other contract is refused with APN_ALLOWLIST_REFUSED (allowlist_asset_unlisted) before any RPC call.
  • A symbol is not an identity. Select a token by its exact contract address.
  • Enabling a network for direct transfers enables nothing else.

Which owner allowlist rail applies to EVM transfers?

The direct rail. Each asset needs its own "rail": "direct" admission in the owner's apn.allowlist-policy-file.v1 file, with accounts.evm set to the local wallet address. Caps are in atomic units of the asset. The per-operation and daily caps apply to native coins and tokens alike. See security.

{ "chain": "eip155:10", "kind": "native", "rail": "direct", "maximumPerTransferAtomic": "1200000000000000", "dailyLimitAtomic": "4000000000000000" }
{ "chain": "eip155:43114", "kind": "token", "identifier": "0x9702230A8Ea53601f5cD2dc00fDBc13d4dF4A8c7", "rail": "direct", "maximumPerTransferAtomic": "3000000", "dailyLimitAtomic": "10000000" }

These two rows are the repository's examples: native ETH on OP Mainnet and USDT on Avalanche. The caps are examples only. Nothing in APN defaults to them.

  • Without an active policy, every direct transfer is refused with allowlist_policy_required.
  • An asset without its own admission is refused with allowlist_direct_not_admitted, even when the same symbol is admitted on another network.
  • An admission can add a recipients list of 1 to 16 addresses. A recipient outside the list is refused with allowlist_recipient_not_admitted before anything is signed.
  • x402 purchases and gasless transfers use their own admissions: the profile policy for local x402, the gasless rail for gasless. See x402 and gasless.

How do I send ETH or USDC from an AI agent on Base?

You need a local wallet profile, an active allowlist policy that admits the asset on the direct rail, and funds. Funds means the asset amount plus native coin for the fee. Every command also needs an explicit --rpc-url. There is no default endpoint on the money path. If you have not installed APN yet, start with install and the quickstart.

apn wallet balance --profile default --chain eip155:8453 --asset native --rpc-url <https-base-rpc-url>
apn pay transfer prepare-asset --profile default --chain eip155:8453 --asset native --to <recipient> \
  --amount 0.000001 --max-fee-wei <owner-budget> --idempotency-key <unique-key> --rpc-url <https-base-rpc-url>
apn pay transfer approve --operation <operation-id> --rpc-url <https-base-rpc-url>     # foreground terminal
apn operation status --operation <operation-id>
apn operation resume --operation <operation-id> --rpc-url <https-base-rpc-url>
apn receipt get --operation <operation-id>

For a token, replace native with its pinned contract. Without --chain and --asset, wallet balance reads Base ETH and canonical Base USDC.

  • --max-fee-wei is required. It is the pre-submission budget for the total fee quote in wei-scale units. It is not an onchain-enforced fee cap.
  • --amount is a canonical exact positive decimal. APN does not round.
  • --idempotency-key is 8 to 200 safe ASCII characters.
  • --rpc-url is a credential-free public HTTPS endpoint of the selected chain.

Approval is a foreground terminal step. Over MCP, apn_wallet_balance and apn_pay_transfer_prepare_asset run the same code as the CLI. Approval is not an MCP tool: apn_foreground_handoff only returns the CLI command for a human to run.

How does APN price gas on each EVM network?

Every network signs an EIP-1559 transaction with maxFeePerGas = 2 x latest baseFeePerGas + priority fee. APN freezes gas x maxFeePerGas as the maximum execution fee. --max-fee-wei caps the total quote, including any L1 data fee and operator fee. A quote above the budget is refused with APN_FEE_BUDGET_EXCEEDED. Too little native balance is refused with APN_INSUFFICIENT_GAS.

  • Ethereum, Polygon, Avalanche, Linea, Sei, BNB: execution fee only. BNB has a zero base fee, so the priority fee is the whole price.
  • Base, OP Mainnet, Unichain: the quote adds an L1 data fee upper bound and the operator fee from the GasPriceOracle predeploy 0x420000000000000000000000000000000000000F.
  • Arbitrum One: one gas envelope covers L2 execution and L1 posting (feeModel: arbitrum-inclusive). --priority-fee-wei is refused there.
  • Monad: the network charges the gas limit, not gas used (feeModel: monad-gas-limit).

--priority-fee-wei replaces the RPC's tip suggestion with the owner's tip, because some public RPCs answer 0. A finished transfer reports what it paid in actual_network_fee.

Which RPC endpoint should an agent use?

The selected --rpc-url must serve the chosen chain and must accept JSON-RPC batch requests. An endpoint that answers a batch with a single object fails with APN_RPC_PROTOCOL and reason rpc_batch_unsupported. An endpoint on the wrong chain fails with APN_CHAIN_MISMATCH.

The EVM assets guide lists keyless endpoints that accepted batches for all eleven networks, and the ones that refused. Provider limits change, so treat it as a starting point.

When does APN call an EVM transfer complete?

  • Inclusion networks (Ethereum, Base, OP Mainnet, Unichain, Linea, Polygon): a canonical receipt at the RPC's latest head. That is inclusion, not irrevocable finality.
  • Safe networks (Arbitrum One, BNB, Avalanche, Monad, Sei): the receipt block must also be at or below the RPC's safe head. This trusts the RPC.
  • ERC-20 transfers also need the receipt's sole Transfer log out of the sender to carry the exact amount to the exact recipient from the pinned token. A hash alone never proves a token payment.

What happens if the agent or the network fails mid-transfer?

Chain, asset, amount, recipient, payer, nonce and fee budget are frozen at prepare. Repeating the same request returns the existing operation. Changing material inputs under the same idempotency key is a conflict. For the full model see recovery.

  • Every check that can refuse (policy, funding, fees, nonce) runs before signing. After a restart APN retrieves only the saved signature, or fails before effect. It never signs a replacement.
  • If the approving command finds no receipt, the state is submitted_pending. apn operation resume --operation <id> --observe-only true --rpc-url <url> inspects it without custody access and never broadcasts.
  • If no receipt exists and the sender's finalized nonce has not passed the frozen one, a plain resume sends the same signed bytes again. Hash and nonce are unchanged, so the amount moves at most once.
  • If the finalized nonce has passed and no node knows the transaction, the transfer ends failed_proven_superseded and nothing is sent.
  • A prepared transfer must be approved within 10 minutes. The next prepare-asset on the same profile, network and account retires an expired unsigned transfer as failed_before_effect with reason approval_window_expired.
  • apn operation abandon closes an undecidable transfer after foreground acknowledgement. A dispatched one ends abandoned_unknown and its usage hold stays charged.

Can the agent read or revoke an ERC-20 allowance?

Yes. status reads one allowance of the local wallet. revoke sends approve(spender, 0) and nothing else. Because revoking only removes a permission, no asset admission applies. Both commands read through the chain's APN_<CHAIN>_RPC_URL variable, for example APN_BASE_RPC_URL.

apn wallet allowance status --profile <profile> --chain eip155:<id> --asset <token-address> --spender <address>
apn wallet allowance revoke --profile <profile> --chain eip155:<id> --asset <token-address> --spender <address> \
  --max-gas-limit <uint> --max-fee-per-gas-wei <wei> --max-priority-fee-per-gas-wei <wei>

Over MCP, revoke returns the CLI handoff. Repeating the command continues the open revoke and never sends twice.

Which wallet profiles support direct EVM transfers?

Only the local encrypted wallet supports direct native and listed-token transfers, on all eleven networks. Coinbase Agentic Wallet, MetaMask Agent Wallet and MetaMask Smart Account do not.

The provider profiles have their own routes for Base USDC. See wallets. For USDC transfers whose fee is paid from the USDC amount, without native gas, see gasless. To move funds between chains, see bridges.

Questions

Which EVM networks does APN support for direct transfers?

Eleven: Ethereum, Base, Arbitrum One, OP Mainnet, Polygon PoS, BNB Smart Chain, Avalanche C-Chain, Unichain, Linea, Monad and Sei EVM. Each has pinned native and token rows, listed in the table above.

Can an AI agent send any ERC-20 token with APN?

No. Direct transfers accept only the pinned contracts. Any other contract is refused with allowlist_asset_unlisted before any RPC call.

Can the agent approve its own transfer?

No. Approval is a foreground terminal step with a typed code. MCP only returns the command for a human to run.

Sources
  1. evm-assets.md: networks, assets, commands, fees, RPC, recovery
  2. allowlist-direct-integration.md: direct rail and refusals
  3. allowlist-policy.md: rails, caps, recipient pins
  4. README: how APN works, MCP never approves