Aggregate wallet stats (tx count, volume, unique recipients) from the x402 protocol explorer.
What it does
This endpoint returns aggregate statistics for a specific wallet address within the x402 payment ecosystem. It is part of x402scan, a payment data explorer and analytics dashboard for the x402 protocol, built by Merit Systems. The wallet stats endpoint provides metrics such as transaction count, total transfer amount, and unique recipients for any wallet that has sent x402 micropayments on Base or Solana.
The endpoint accepts optional query parameters to filter by chain (base or solana) and timeframe (1, 7, 14, or 30 days lookback). It is a GET request that costs $0.01 per call, paid via the x402 micropayment protocol. The specific URL listed here includes a hardcoded wallet address (0x2e2e…bb6), but the underlying operation (x402_wallets_stats) works with any valid wallet address substituted into the path.
Note: During probing, this specific URL returned 404 rather than the expected 402 challenge. The canonical path documented in the OpenAPI spec is /api/x402/wallets/{address}/stats, while this endpoint uses /api/data/wallets/{address}/stats. The /api/data/ prefix may be a legacy or alternative route that is no longer active. The broader x402scan service and its OpenAPI-documented endpoints appear healthy (root returns 200).
Capabilities
Use cases
- —Retrieve aggregate payment statistics for a specific x402 sender 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 per wallet
Fit
Best for
- —Agents needing quick wallet-level summaries without paginating through individual transactions
- —Analytics pipelines monitoring x402 ecosystem participation
- —Developers building on top of x402 protocol who need sender-side metrics
Not for
- —Looking up merchant/recipient stats (use the merchants/{address}/stats endpoint instead)
- —Fetching individual transaction details (use wallets/{address}/transactions instead)
- —Non-x402 blockchain data (this only covers x402 protocol transfers)
Quick start
curl -H "X-Payment: <x402_payment_header>" \
"https://www.x402scan.com/api/x402/wallets/0x2e2e566e1091fc42c6f1cec919ab1320b2899bb6/stats?chain=base&timeframe=7"Endpoint
Quality
The OpenAPI spec is thorough and documents the canonical endpoint well with clear pricing and parameters. However, the actual listed URL (/api/data/wallets/…) returned 404 on both GET and POST, suggesting it may be a stale or incorrect path versus the documented /api/x402/wallets/… route. No response schema or example responses are provided in the spec.
Warnings
- —The listed endpoint path /api/data/wallets/{address}/stats returned 404; the canonical OpenAPI path is /api/x402/wallets/{address}/stats — the listed URL may be outdated or incorrect.
- —No response schema or example response is documented in the OpenAPI spec.
- —The hardcoded wallet address in the URL may not have any activity; the endpoint is parameterized by address.
Citations
- —The wallet stats endpoint costs $0.01 per call via x402 micropaymenthttps://www.x402scan.com
- —x402scan is a payment data explorer and registry for the x402 protocol, built by Merit Systemshttps://www.x402scan.com
- —The endpoint supports chain filter (base, solana) and timeframe filter (1, 7, 14, 30 days)https://www.x402scan.com
- —The canonical OpenAPI path is /api/x402/wallets/{address}/statshttps://www.x402scan.com