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. Given a wallet address, the endpoint returns metrics such as transaction count, total transfer amount, and unique recipients for that wallet's outbound (sender) activity.
The endpoint supports optional query parameters to filter by chain (Base or Solana) and timeframe (1, 7, 14, or 30 days lookback). It is a GET request priced at $0.01 per call, payable via the x402 micropayment protocol. The x402 payment is made by including an X-Payment header in the request.
Note: The specific URL listed here hardcodes a particular wallet address (0x741244cb38d299d154e5cc40f9309250a5cf5c7c). The generic pattern is `/api/x402/wallets/{address}/stats`. During probing, this specific URL returned 404 on both GET and POST, which may indicate the address has no indexed data or the endpoint path has changed. The broader x402scan origin is live (HTTP 200 on root) and serves a comprehensive OpenAPI spec describing this and many other data endpoints.
Capabilities
Use cases
- —Retrieve aggregate spending stats for a wallet that has made x402 payments
- —Monitor a wallet's transaction count and volume over configurable time windows
- —Compare wallet activity across Base and Solana chains
- —Build dashboards tracking x402 protocol adoption per wallet
- —Audit outbound USDC micropayment activity for a specific address
Fit
Best for
- —Agents needing quick wallet-level x402 payment summaries
- —Analytics pipelines tracking x402 ecosystem activity
- —Developers building on top of the x402 protocol who need sender-side metrics
Not for
- —General-purpose blockchain explorers (this only covers x402 protocol transfers)
- —Querying merchant/recipient stats (use the merchants/{address}/stats endpoint instead)
- —Real-time streaming transaction feeds
Quick start
curl -H "X-Payment: <x402_payment_token>" \
"https://www.x402scan.com/api/x402/wallets/0x741244cb38d299d154e5cc40f9309250a5cf5c7c/stats?chain=base&timeframe=7"Endpoint
Quality
The OpenAPI spec is thorough and clearly documents the endpoint pattern, pricing ($0.01), parameters, and protocol. However, the specific hardcoded URL returned 404 during probing (not a 402 challenge), no response schema or example response is provided in the spec, and no dedicated docs page exists. The endpoint may work for addresses with indexed data but could not be confirmed live at this exact URL.
Warnings
- —Probe returned 404 on both GET and POST for this specific wallet address — the address may have no indexed data, or the URL path may differ from the OpenAPI pattern (note: listed URL uses /api/data/wallets/ but OpenAPI spec uses /api/x402/wallets/)
- —No response schema or example response is documented in the OpenAPI spec
- —The listed endpoint path (/api/data/wallets/...) does not match the OpenAPI spec path (/api/x402/wallets/...) — the correct base path is likely /api/x402/wallets/{address}/stats
Citations
- —Endpoint is priced at $0.01 per call via x402 micropaymenthttps://www.x402scan.com
- —Supports chain filter (base, solana) and timeframe filter (1, 7, 14, 30 days)https://www.x402scan.com
- —x402scan is described as a payment data explorer and registry for the x402 protocol, built by Merit Systemshttps://www.x402scan.com
- —The OpenAPI spec lists the wallet stats endpoint as GET /api/x402/wallets/{address}/statshttps://www.x402scan.com