Stablecoin routing for AI agent transactions · which stablecoin actually settles agent payments

TL;DR

When an AI agent pays for an API call, a tool invocation, or a downstream agent service, the actual on-the-wire settlement asset in mid-2026 is USDC on Base for the dominant share, USDC on other L2s (Arbitrum, Optimism, Polygon PoS, Solana) for chain-specific use cases, USDT on Tron / Ethereum L1 for emerging-market and informal agent rails, and USDB / RLUSD / PYUSD / FDUSD for issuer-aligned vertical stacks. The routing is not the agent’s choice in most stacks — it is the wallet provider’s and the receiving merchant’s choice. Privy + Coinbase CDP default to USDC, and Stripe / Bridge route through USDB, so the default-tier wallet split (see 2026 embedded-wallet consolidation) effectively decides which stablecoin AI agents pay in. Gasless transfers via ERC-4337 paymasters and Circle CCTP v2 (fast cross-chain finality) determine the UX of multi-chain agent payments, and the x402 protocol is the dominant HTTP-layer mechanism that carries the choice. See USD stablecoin interchange for the wider stablecoin market and chain × token × strategy trilemma for issuer strategy.

Wiki route

This entry sits under agent-economy index. Read it with x402 HTTP payment overview for the protocol that carries the settlement, AP2 overview for the intent / mandate layer, Coinbase CDP developer platform for the USDC-on-Base default, and fintech index for the broader stablecoin reserve and interchange context.

Which stablecoin · 2026 mid-year settlement mix

A rough public-source-derived breakdown of where agent-payment volume actually lands by stablecoin / chain combination in mid-2026:

Stablecoin × chain	Approximate routing share	Driver
USDC on Base	dominant share for default-tier embedded wallets	Coinbase CDP default + Base Paymaster + AgentKit
USDC on Ethereum L1	enterprise / institutional agent flows	Compliance posture + USDC primary issuance
USDC on Arbitrum	DeFi-integrated agent flows	Arbitrum’s deep DeFi liquidity
USDC on Optimism	OP-Stack-aligned agent flows	OP Superchain coordination
USDC on Solana	high-throughput agent flows	Solana’s low-latency settlement; Privy + CDP multi-chain support
USDT on Tron	emerging-market and informal agent rails	USDT’s regional dominance, low fees on Tron
USDT on Ethereum L1	legacy and CEX-routed flows	USDT remains largest stablecoin by float
USDB on Tempo	Stripe-aligned agent flows	Stripe vertical stack default
RLUSD on XRP Ledger + Ethereum	Ripple-aligned flows	Ripple corridors and corporate-treasury demand
PYUSD on Ethereum + Solana	PayPal-aligned flows	PayPal merchant payouts
FDUSD on Ethereum + BNB	Asia-CEX-aligned flows	Binance routing

Two observations:

USDC on Base is the de facto default because the AWS AgentCore default-wallet duopoly (Privy + CDP) routes the long tail of agent provisioning toward Coinbase-aligned chain economics.
USDT is structurally relevant for emerging-market / informal rails even though no major hyperscaler-default agent stack picks it as the recommended default.

Settlement finality requirements

An agent transaction’s tolerance for settlement-finality delay depends on the use case:

Use case	Tolerance	Typical chain choice
Per-API-call x402 micro-payment for a public endpoint	Sub-second perceived finality (probabilistic acceptance is OK)	L2 with fast block times; Base, Solana
Agent-to-agent settlement for a multi-second tool invocation	Few-second finality	Base, Arbitrum, Optimism
Agent paying a downstream agent that holds custody (escrow-like)	Hard finality required	Ethereum L1, or wait for L2 → L1 fraud-window confirmation
Cross-border B2B agent settlement	Finality + compliance	USDC on Ethereum L1; CCTP v2 cross-chain
Treasury sweep	Hard finality + reconciliation	Ethereum L1; off-chain reconciliation to traditional accounting

The category trade-off mirrors the way payment networks balance authorization (fast) and clearing (slow). Agents typically operate against x402 HTTP 402 semantics, which accept early on-chain inclusion as authorization and treat full finality as a separable reconciliation step.

Cross-chain abstraction · how multi-chain agent UX works

Most agent SDKs do not expose the underlying chain to the agent’s reasoning layer. The chain-abstraction stack:

Wallet-balance API. Privy’s Multichain Balances API and CDP’s wallet APIs return a unified USDC balance across Ethereum, Base, Arbitrum, Optimism, and Polygon. The agent sees “you have N USDC available” rather than chain-by-chain balances.
Routing layer. The wallet routes outgoing payments to the lowest-fee, fastest-finality chain that the merchant accepts. The agent does not pick the chain.
Circle CCTP v2 (Cross-Chain Transfer Protocol). Circle’s burn-and-mint mechanism for USDC across supported chains. CCTP v2 (released 2025) supports faster soft-finality across L2s with a hooks model for programmable post-mint actions. CCTP is the foundation of much of the multi-chain USDC routing inside default-tier wallets.
LayerZero / Wormhole / Hyperlane / Axelar. General-purpose cross-chain messaging layers used for non-USDC stablecoins, longer-tail chains, and cross-stack token swaps. These are typically wrapped behind the wallet abstraction.
Cross-chain intent layer. Across, Catalyst, Bungee, and similar intent-based routing protocols allow the agent’s wallet to publish an intent (“move 100 USDC to chain X”) and have a network of solvers fulfill it competitively.

The pattern in default-tier embedded wallets is to default to USDC + CCTP v2 for cross-chain routing and to fall back to general-purpose messaging only when the target chain lacks USDC + CCTP support.

Gasless agent transactions · paymaster mechanics

Agents do not hold ETH for gas in any sensible production deployment. Gas is sponsored via ERC-4337 paymasters:

Coinbase Base Paymaster. Sponsors gas for transactions inside CDP-issued Smart Wallets on Base, paid in USDC or sponsored outright. The structural default for the CDP / AgentKit stack.
Pimlico, Stackup, Biconomy, Alchemy AA paymaster. Third-party paymasters that any ERC-4337 wallet can integrate. Used by Privy and other SDKs.
Stripe / Privy custom paymaster. Stripe-rail-aware paymasters that meter USDC out of a merchant’s Stripe Treasury balance.
EIP-7702 hybrid mode. EOAs can temporarily upgrade to smart accounts (see ERC-7715 permission model) for a single transaction, allowing paymaster sponsorship without permanent migration.

For an agent making thousands of micro-payments per day, the paymaster’s gas-cost model is a primary economic input. Base’s USDC-native gas + sub-cent per-transaction fee is the structural reason Base dominates default-tier agent payment routing.

Circle CCTP v2 · the cross-chain backbone

CCTP v2 (Circle Cross-Chain Transfer Protocol version 2) released in 2025 is the most consequential agent-stack stablecoin infrastructure change of the year. Key properties from Circle’s developer documentation:

Burn-and-mint, not bridge-and-wrap. USDC is burned on the source chain and minted on the destination chain by Circle’s attestation. There is no bridged-USDC variant — every USDC on every CCTP-supported chain is native USDC.
Soft-finality fast transfers. CCTP v2 introduced a fast-transfer mode that uses a finality-threshold attestation rather than waiting for hard L1 finality, supporting sub-minute cross-chain settlement for the common case.
Hooks. A post-mint hook lets the destination chain run a programmable action after the USDC is minted. For agent payments this enables atomic “receive USDC + call downstream tool” semantics.
Chains supported. Ethereum L1, Base, Arbitrum, Optimism, Avalanche, Polygon PoS, Solana, plus additional chains added through 2025-2026.

For an AI agent that needs to pay a tool on a different chain than its wallet currently holds USDC, CCTP v2 is the structural default. The wallet provider can resolve the cross-chain difference transparently within seconds.

x402 + USDC · the dominant agent-payment HTTP stack

The x402 protocol (Coinbase, 2025-05) revives the HTTP 402 Payment Required status code and binds it by default to USDC on Base for the reference implementation. The agent flow:

Agent calls an API endpoint.
Server responds HTTP 402 with payment instructions (USDC amount + recipient chain + address).
Agent wallet (Privy / CDP) signs and submits a USDC transfer.
Server verifies the transfer (Circle CCTP attestation or chain-native confirmation), returns the requested resource.

The protocol is asset-agnostic in its design, but the reference + AWS AgentCore default + Cloudflare Agents integration default all use USDC. The x402 Bazaar MCP catalog (10,000+ endpoints by mid-2026) is predominantly USDC-priced.

Issuer-aligned vertical stacks

The non-USDC, non-USDT stablecoin slice of agent payment volume is driven by issuer-aligned vertical stacks:

USDB (Stripe / Bridge). Inside the Stripe five-layer stack (Connect → Privy → Bridge USDB → Tempo → AP2 / x402), USDB is the default settlement asset for Stripe-rail agent payments.
RLUSD (Ripple). Used inside Ripple corridors and for Ripple-integrated corporate-treasury agent payments.
PYUSD (PayPal). Used for PayPal-aligned merchant agent payouts on Ethereum + Solana.
FDUSD (First Digital). Used in Binance / FDIC-perimeter Asian-CEX agent routing; relevant where Binance’s BNB / FDUSD pair is the on-ramp.
JPYC / DCJPY / Progmat JPY (Japan). Used inside Japan’s deposit-token + EPI integration flows for agents operating in JPY-denominated commerce.

The pattern is that each vertically-integrated payment stack runs its own stablecoin as the default within that stack, and CCTP-style cross-chain interop is only USDC-internal. Cross-stablecoin liquidity sits in DEXs (Curve) and CEX market-makers — see USD stablecoin interchange.

Agent permission · who picks the stablecoin

The hierarchy of “who decides” in a typical agent payment:

Hyperscaler default. AgentCore Payments default = Privy or CDP wallet, which means USDC on the chain the wallet defaults to (Base for CDP, multi-chain for Privy).
Wallet provider default. Within that wallet, the multichain balances API tells the agent it has USDC; the wallet picks the chain at routing time.
Merchant acceptance. The recipient publishes which stablecoin / chain combinations it accepts. The wallet matches.
Agent intent. Only in narrow cases does the agent itself reason about the choice — for example, a treasury-agent rebalancing across stablecoins.
User mandate via ERC-7715. The user’s ERC-7715 wallet permission can constrain stablecoin / chain choices (allowed list of denominations and venues).

For most agent runtimes, the agent neither knows nor cares about the underlying stablecoin / chain. The choice is structural to the wallet stack.

Sources

x402 protocol public documentation (x402.org)
Coinbase Developer Platform public documentation (docs.cdp.coinbase.com)
Privy public documentation (docs.privy.io)
Circle Cross-Chain Transfer Protocol public documentation (circle.com, developers.circle.com/cctp)
Ethereum EIPs: EIP-4337 (account abstraction), EIP-7702 (EOA upgrade), EIP-7715 (wallet permissions)
Base, Arbitrum, Optimism public chain documentation
Google Agentic Commerce AP2 public repository (github.com/google-agentic-commerce/AP2)
US Federal Reserve, FSA Japan, FCA UK, and MAS Singapore public materials on stablecoin classification and settlement