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 in 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 endpoint is located at `/api/x402/wallets/{address}/stats` but the listed URL hardcodes a specific wallet address (0xfbd8021dbfa95c0d4125b381bd925a018a1399c9).
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. According to the OpenAPI spec, the endpoint costs $0.01 per call, paid via the x402 micropayment protocol.
Note: The probe returned 404 on both GET and POST for this specific URL. The OpenAPI spec defines the canonical path as `/api/x402/wallets/{address}/stats`, but the listed URL uses `/api/data/wallets/{address}/stats` (with an extra `/data/` segment). This path mismatch likely explains the 404. The broader x402scan service is live (root returns 200) and the OpenAPI spec documents the correct wallet stats endpoint at the `/api/x402/` path prefix.
Capabilities
Use cases
- —Retrieve aggregate sending statistics for a specific wallet address in the x402 ecosystem
- —Monitor wallet activity over configurable time windows (1, 7, 14, or 30 days)
- —Compare wallet behavior across Base and Solana chains
- —Build dashboards tracking x402 protocol adoption by wallet
Fit
Best for
- —Agents needing quick wallet-level summaries without paginating through individual transactions
- —Analytics pipelines monitoring x402 protocol usage
- —Developers building x402 ecosystem tooling
Not for
- —Querying non-x402 on-chain transactions or general blockchain data
- —Retrieving individual transaction details (use the transactions endpoint instead)
- —Wallets that only receive payments (use the merchant stats endpoint instead)
Quick start
curl -H 'X-Payment: <x402_payment_header>' \
'https://www.x402scan.com/api/x402/wallets/0xfbd8021dbfa95c0d4125b381bd925a018a1399c9/stats?chain=base&timeframe=7'Endpoint
Quality
The OpenAPI spec is detailed with clear parameter definitions and pricing, but the actual listed endpoint URL uses a /api/data/ path that returns 404, suggesting a path mismatch. No response schema or example responses are provided. The correct canonical path appears to be /api/x402/wallets/{address}/stats.
Warnings
- —The listed endpoint URL (/api/data/wallets/.../stats) returned 404 on both GET and POST. The OpenAPI spec defines the canonical path as /api/x402/wallets/{address}/stats — the /data/ segment appears incorrect.
- —No response schema or example response is documented in the OpenAPI spec.
- —The endpoint is hardcoded to a single wallet address; the generic parameterized path is /api/x402/wallets/{address}/stats.
Citations
- —The 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 canonical wallet stats endpoint path is /api/x402/wallets/{address}/stats with optional chain and timeframe parametershttps://www.x402scan.com
- —Supported chains are Base and Solana; timeframe options are 1, 7, 14, or 30 dayshttps://www.x402scan.com