Aggregate wallet stats (tx count, volume, unique recipients) for any x402 sender address.
What it does
This endpoint returns aggregate statistics for a specific wallet address acting as a sender (buyer) in the x402 payment ecosystem. It is part of x402scan, a payment data explorer and analytics platform for the x402 protocol built by Merit Systems. The endpoint is located at `/api/x402/wallets/{address}/stats` but the listed URL hardcodes a specific wallet address (0xf8c0ace1f445715e1800396922590ce066da4f7d).
The endpoint accepts optional query parameters to filter by chain (Base or Solana) and timeframe (1, 7, 14, or 30 days lookback). It returns aggregate data such as transaction count, total amount sent, and unique recipients for the specified wallet. The data covers USDC transfers processed through x402 facilitators like Coinbase, PayAI, and Meridian.
Pricing is $0.01 per request, paid via the x402 micropayment protocol. Note that the probe returned 404 on both GET and POST for this specific hardcoded-address URL, which may indicate the particular wallet has no indexed data or the URL path uses a different routing scheme than the OpenAPI spec's parameterized path `/api/x402/wallets/{address}/stats`. The canonical parameterized endpoint is documented in the OpenAPI spec and should work with valid wallet addresses.
Capabilities
Use cases
- —Retrieve aggregate spending stats for a specific x402 buyer wallet
- —Monitor wallet activity over configurable time windows (1/7/14/30 days)
- —Compare wallet behavior across Base and Solana chains
- —Build dashboards tracking x402 protocol adoption by wallet
Fit
Best for
- —Agents needing on-chain x402 payment analytics for a specific sender address
- —Developers building x402 ecosystem monitoring tools
- —Analysts tracking USDC micropayment flows on Base and Solana
Not for
- —Looking up arbitrary ERC-20 or SPL token transfers outside the x402 ecosystem
- —Querying merchant/recipient stats (use the merchants/{address}/stats endpoint instead)
- —Free or API-key-authenticated access — requires x402 micropayment per call
Quick start
curl -H "X-Payment: <x402_payment_header>" \
"https://www.x402scan.com/api/x402/wallets/0xf8c0ace1f445715e1800396922590ce066da4f7d/stats?chain=base&timeframe=7"Endpoint
Quality
The OpenAPI spec is well-documented with clear parameters and pricing, but the probe returned 404 for this specific hardcoded wallet address (not a standard 402 challenge), no response schema is provided, and no example responses are available. The endpoint may work with other addresses but liveness for this specific URL is unconfirmed.
Warnings
- —Probe returned 404 on both GET and POST for this specific wallet address — the endpoint may only return data for wallets with indexed x402 activity
- —No response schema documented in the OpenAPI spec; response structure must be inferred
- —The listed URL hardcodes a single wallet address rather than being a parameterized endpoint
Citations
- —Endpoint is documented as GET /api/x402/wallets/{address}/stats returning aggregate stats (tx count, total amount, unique recipients)https://www.x402scan.com
- —Price is $0.01 per request via x402 micropaymenthttps://www.x402scan.com
- —Supports chain filter (base, solana) and timeframe filter (1, 7, 14, or 30 days)https://www.x402scan.com
- —x402scan is a payment data explorer and registry for the x402 protocol, built by Merit Systemshttps://www.x402scan.com