Skip to main content
Agent Wallet implements x402 specification v2 — the open protocol for machine-to-machine stablecoin payments over HTTP. This page covers what Agent Wallet provides and how it differs from other x402 implementations. For a full protocol explainer, see the x402 official documentation.

​
What Agent Wallet Provides

Most x402 implementations support a single stablecoin on a single chain (typically USDC on Base). Agent Wallet supports multiple assets across multiple chains:
StablecoinSupported Chains
USDCBase, Solana
FDUSDBSC, Arbitrum, Ethereum, Solana
Coming soon: FDUSD support on SUI.
Your agent’s wallet needs to hold the required stablecoin on the chain the merchant accepts. When a merchant supports multiple options, the wallet selects the best match from what’s available in your balance.

​
x402 Tools

Agent Wallet provides two tools for x402 payments, available through both the CLI and the MCP server. Which one to use depends on the agent’s environment and capabilities. Signs the payment authorization only — the agent handles the HTTP communication with the resource server itself. How it works:
  1. Agent calls the resource server and receives HTTP 402 Payment Required with payment requirements (accepts[] array with chain, token, amount, recipient)
  2. Agent passes the requirements to authorizePayment — the wallet selects the best payment option from the agent’s balance and signs an EIP-3009 transferWithAuthorization
  3. Agent retries the original request with the signed PaymentPayload attached
  4. The resource server’s facilitator verifies and settles the payment on-chain
This gives the agent maximum autonomy. The agent understands what’s happening at each step, makes its own decisions about whether to pay, and handles the HTTP communication directly. The wallet’s role is limited to what it should be: signing the payment authorization.
EIP-3009 means the payment is gasless for the payer — the facilitator executes the on-chain transfer, not the agent’s wallet.
When using the Finance District CLI Skills, the skill teaches the agent the full x402 protocol flow and guides it to use authorizePayment at the right step.

​
getX402Content (Fallback)

Bundles the entire x402 flow — initial HTTP request, authorization signing, and retry — into a single call. The agent provides the resource URL, and the wallet handles everything internally. Use this when the agent cannot make HTTP requests directly (e.g. web-based AI assistants like Claude Desktop or Cursor that have MCP access but cannot execute shell commands or make outbound HTTP calls).

​
Choosing the Right Tool

ToolAgent handles HTTPBest for
authorizePaymentYesAgents with HTTP access — Claude Code, OpenClaw, autonomous agents, agent frameworks
getX402ContentNoAgents without HTTP access — Claude Desktop, Cursor, web-based assistants

​
Try It Out

With authorizePayment:
“Access the premium data API at https://api.example.com/market-data”
The agent handles the 402 response, requests payment signing from the wallet, and retries with proof. With getX402Content:
“Pay for the API at https://api.example.com/market-data”
The wallet handles the full flow and returns the content. Direct payment:
“Pay 2 USDC to 0xABC…123 on Base”
The agent can also make explicit payments to known addresses without encountering a 402 flow.

​
Agent Wallet + Prism

X402 is where the two Finance District products meet:
  • Agent Wallet is the buyer side — your agent has funds and wants to pay for services
  • Prism is the seller side — merchants accept stablecoin payments from AI agents
When an Agent Wallet pays a Prism merchant via x402, the transaction stays within one ecosystem. The agent pays, Prism verifies, the merchant gets their funds.

Prism Overview

Learn how merchants accept agent payments

X402 Protocol

How Prism implements x402 on the merchant side

CLI Skills

Install the skills that teach agents x402

x402.org

Official x402 protocol specification
Last modified on March 30, 2026