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 built by Merit Systems that indexes x402 protocol transfers on Base and Solana chains.
The wallet stats endpoint (`GET /api/x402/wallets/{address}/stats`) provides summary metrics such as transaction count, total transfer amount, and unique recipients for a given sender address. Results can be filtered by chain (Base or Solana) and by timeframe (1, 7, 14, or 30 days lookback). The endpoint costs $0.01 per call, paid via an x402 micropayment in the X-Payment header.
Note: The specific URL listed here embeds a hardcoded wallet address (`0xa6c89c66265b02d8635f843615250424efb3e29d`) in a non-standard path segment (`/api/data/wallets/...` instead of `/api/x402/wallets/...`). The probe returned 404 on both GET and POST, suggesting this particular URL variant is not a valid route. The canonical endpoint documented in the OpenAPI spec is `/api/x402/wallets/{address}/stats`. x402scan also offers sibling endpoints for merchant stats, transaction histories, facilitator analytics, resource search, and a USDC send capability.
Capabilities
Use cases
- —Retrieve aggregate spending stats for a wallet that has made x402 payments
- —Monitor transaction volume and unique recipient counts for a specific sender address
- —Filter wallet activity by chain (Base or Solana) and time window
- —Build dashboards tracking x402 protocol adoption per wallet
- —Audit agent spending across x402-enabled APIs
Fit
Best for
- —Agents or dashboards needing quick wallet-level x402 spending summaries
- —Developers building analytics on top of the x402 payment protocol
- —Monitoring wallets that interact with x402-protected APIs
Not for
- —General-purpose blockchain explorers (this only covers x402 protocol transfers)
- —Querying non-USDC token transfers or arbitrary on-chain data
- —Free/unauthenticated access — every call requires a $0.01 x402 micropayment
Quick start
curl -X GET \
'https://www.x402scan.com/api/x402/wallets/0xa6c89c66265b02d8635f843615250424efb3e29d/stats?chain=base&timeframe=7' \
-H 'X-Payment: <x402_payment_token>'Endpoint
Quality
The OpenAPI spec is well-documented with clear parameters and pricing, but the specific listed endpoint URL (/api/data/wallets/...) returned 404 on probe — it does not match the canonical /api/x402/wallets/{address}/stats path. No response schema or example responses are provided. No dedicated docs page exists.
Warnings
- —The listed endpoint URL uses '/api/data/wallets/' which returned 404; the correct canonical path per the OpenAPI spec is '/api/x402/wallets/{address}/stats'.
- —No response schema or example response is documented in the OpenAPI spec.
- —No dedicated documentation page found (/docs, /api, /pricing all return 404).
Citations
- —The endpoint costs $0.01 per call via x402 micropaymenthttps://www.x402scan.com
- —Wallet stats endpoint supports chain (base, solana) and timeframe (1, 7, 14, 30 days) query parametershttps://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 canonical path is /api/x402/wallets/{address}/stats per the OpenAPI spechttps://www.x402scan.com