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` and accepts an Ethereum or Solana wallet address as a path parameter.
The stats returned cover transaction count, total amount sent, and unique recipients. Optional query parameters allow filtering by chain (base or solana) and timeframe (1, 7, 14, or 30 days lookback). The endpoint costs $0.01 per call, paid via the x402 micropayment protocol using USDC.
Note: The specific URL listed here hardcodes a particular wallet address (`0xd4c940ba609b7e3b0e05caffd042c3e9424bcd29`). The generic pattern is `/api/x402/wallets/{address}/stats`. The probe returned 404 rather than the expected 402 challenge, which may indicate the hardcoded address is not indexed or the endpoint requires a different URL pattern (the OpenAPI spec uses `/api/x402/wallets/{address}/stats` while the listed URL uses `/api/data/wallets/{address}/stats`). The OpenAPI spec documents the endpoint under `/api/x402/` not `/api/data/`, so the listed URL path may be incorrect.
Capabilities
Use cases
- —Retrieve aggregate spending stats for a specific wallet address in the x402 ecosystem
- —Monitor how much a wallet has spent via x402 payments over configurable time windows
- —Identify unique merchants/recipients a wallet has transacted with
- —Compare wallet activity across Base and Solana chains
Fit
Best for
- —Agents that need to audit or summarize x402 spending for a given wallet
- —Analytics dashboards tracking x402 protocol adoption per wallet
- —Compliance or accounting workflows that need sender-side transaction summaries
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 transaction data
Quick start
curl -H 'X-Payment: <x402_payment_token>' \
'https://www.x402scan.com/api/x402/wallets/0xd4c940ba609b7e3b0e05caffd042c3e9424bcd29/stats?chain=base&timeframe=30'Endpoint
Quality
The OpenAPI spec is well-documented with clear parameters and pricing, but the actual listed endpoint URL uses `/api/data/` instead of `/api/x402/` and returned 404 on probe (not the expected 402 challenge). No response schema or example responses are provided. No dedicated docs page exists.
Warnings
- —The listed endpoint path `/api/data/wallets/{address}/stats` does not match the OpenAPI spec path `/api/x402/wallets/{address}/stats` — the URL may be incorrect or outdated.
- —Probe returned 404 on both GET and POST, meaning the endpoint did not return the expected 402 x402 challenge. This could be a path mismatch issue.
- —No response schema or example response is documented in the OpenAPI spec.
- —No dedicated documentation page was found (x402scan.com/docs returns 404).
Citations
- —The endpoint costs $0.01 per call via x402 micropaymenthttps://www.x402scan.com
- —Wallet stats endpoint returns aggregate stats: tx count, total amount, unique recipientshttps://www.x402scan.com
- —Optional query parameters include chain (base, solana) and timeframe (1, 7, 14, or 30 days)https://www.x402scan.com
- —x402scan is built by Merit Systemshttps://www.x402scan.com
- —The OpenAPI spec documents the path as /api/x402/wallets/{address}/statshttps://www.x402scan.com