Payments settled
countx402 payments settled on the latest complete UTC day, counted from facilitator-submitted transfers.
Dashboard · VantagePlanned
x402 Transactions Tracker: Daily Payments and Volume
How many x402 payments settle each day, and how much value do they move on each chain?
x402 payments settled per day, the USDC they move, their size and their chains, counted from the settlement transactions themselves.
ShareEmail it
Blueprint
What the dashboard will show.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Today
Payments, volume and payers on the latest complete day.
Payment volume
USDCThe face value of the same day's payments, summed.
Median payment
USDCThe median payment amount on the same day.
Distinct payers
countDistinct addresses that paid at least once on the same day.
Payments by chain
countThe day's payments split by the chain they settled on.
Payments by size
countThe day's payments grouped into size buckets, from pay-per-call amounts to larger transfers.
Trend
How payments, volume and payment sizes moved by day and by chain.
Payments in the period
countx402 payments settled over the selected period.
Services paid
countDistinct payTo addresses that received at least one payment over the period.
Median payment by day
USDCThe median payment amount by day, to show whether payments are getting smaller or larger.
Payments and volume by day
countPayments per day stacked by chain, with each day's volume drawn as a line.
- Chain
- Every covered chain, or one of Base, Solana, Polygon and Avalanche
- Period
- Last 7, 30 or 90 days
About
What it answers, and for whom.
x402 is an open payment standard built on the HTTP 402 Payment Required status: a server asks for payment, the client signs a stablecoin transfer and a facilitator settles it on-chain. It lets software agents pay for API calls, data and content one request at a time. This dashboard counts those settlements from the chains themselves: how many payments land each day, how much value they move and on which chains.
Not every signed stablecoin transfer is an x402 payment, so the count starts from the addresses of known facilitators and the transfers they submit. Payments are grouped by size, which separates small pay-per-call payments from larger transfers, and by payer and payee, which shows whether activity comes from many agents or from a few.
Every figure is pinned to the blocks it was counted from, so a daily total can be traced back to the individual settlement transactions and facilitator addresses behind it.
Method
How it will be measured.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →- On EVM chains, a payment is a USDC transferWithAuthorization (EIP-3009) settled by a known x402 facilitator address, read from the AuthorizationUsed and Transfer logs of the same transaction.
- Payments on the Permit2 path that x402's second version added are read from transfers through its proxy contract, and on Solana from SPL token transfers in transactions whose fee payer is a known facilitator.
- Facilitator addresses come from the facilitators' own documentation and public x402 listings, recorded with their source; transfers from unlisted senders are left out rather than guessed.
- Volume is the sum of payment amounts at face value, and sizes are grouped into buckets so that small payments are not hidden by a few large ones.
- Every figure carries a receipt: the blocks or slots, the transaction hashes and the logs it was counted from.
The data it needs
Read from chain state and history
- agent_payments_dailyTo buildAI agents and agent paymentsAgent tokens (supply, holders, trading) and agent payments such as x402 settlements in stablecoins, per day.
- stablecoin_flows_dailyTo buildStablecoin mints, burns and transfersStablecoin mints, burns, transfer volume and active addresses per stablecoin and chain per day.
- address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
- USDC AuthorizationUsed and Transfer logs from transferWithAuthorization calls on Base, Polygon and Avalanche
- Transactions sent by known x402 facilitator addresses, from a facilitator address registry
- Transfers through the x402 Permit2 proxy contract for tokens without EIP-3009
- Solana SPL token transfers in transactions where a known facilitator is the fee payer
- Distinct payer and payTo addresses per day
Questions
Questions people ask.
What is x402?
x402 is an open standard, first published by Coinbase, for paying over HTTP. A server answers a request with status 402 and its price; the client signs a stablecoin payment and retries; a facilitator verifies the signature and settles the transfer on-chain, so the buyer needs no account or API key.
Which chains does x402 run on?
x402 is chain-agnostic: a payment settles on any network that a facilitator supports for the token. It launched on Base, and facilitators have since added Solana, Polygon, Avalanche and other chains. The chain split tile shows where payments actually settle.
What is an x402 facilitator?
The service that checks a signed x402 payment and submits it to the chain, paying the gas. Sellers choose which facilitators they accept. Because the facilitator sends the transaction, its address is how x402 settlements are recognized on-chain.
Are all x402 transactions made by AI agents?
No. The chain records a signed payment and its settlement, not who or what signed it. Payments can come from agents, apps or people; some activity is testing or promotions. This dashboard counts settlements and distinct payers and does not claim to know which are agents.
Why do x402 totals differ between sources?
Sources differ in which facilitators they include, whether they count test networks, which tokens they track and when they cut off a day. This dashboard lists the facilitator addresses it counts and pins every daily total to the blocks it covers.
- HTTP 402
- The Payment Required status code, reserved in early HTTP for future use and adopted by x402 to ask a client for payment.
- EIP-3009
- The transferWithAuthorization function, which lets a token holder sign a transfer that someone else submits and pays gas for. USDC supports it.
- Facilitator
- The x402 service that verifies a signed payment and settles it on-chain on the seller's behalf.
- payTo address
- The address named in a seller's payment requirements, which receives the stablecoin when a payment settles.
Related
More apps like this.
x402 Facilitators and Paid Services Ranked
Which facilitators settle the most x402 payments, which paid services receive the most and how each splits across chains, from settlements.
Multi-chainBaseSolana+2AI Agents in Crypto: Monthly On-Chain Report
A dated monthly review of what AI agents did on-chain: payments settled, agents registered, agent tokens launched and jobs paid.
Multi-chainBaseSolana+2ERC-8004 Agent Registry: Registered AI Agents by Chain
Every AI agent registered under ERC-8004, with its owner, chain, registration date and the reputation feedback it has received.
Multi-chainEthereumBase+3Stablecoin Payments by Transfer Size and Chain
How many stablecoin transfers are payment-sized, from retail to business amounts, on each chain, with trading and exchange flows set apart.
Multi-chainEthereumTron+5Stablecoins on Base: Supply and Transfers
Stablecoin supply on Base coin by coin, from native USDC to EURC and USDS, with the transfers and senders that use it each day.
BaseAI Agent Tokens Ranked by Holders and DEX Volume
AI agent tokens from Virtuals and other agent launchpads, sorted by holders, on-chain trading volume, supply and DEX-implied value.
Multi-chainBaseSolana+1Build x402 Transactions Tracker: Daily Payments and Volume on verified data.
Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.