Aggregate wallet stats (tx count, volume, unique recipients) from the x402 protocol ecosystem for $0.01 per call.
What it does
This endpoint returns aggregate statistics for a specific wallet address within the x402 payment ecosystem. Given a wallet address, it reports metrics such as transaction count, total transfer volume, and unique recipients. The data covers x402 protocol micropayment transfers on Base and Solana chains, and can be filtered by chain and by a timeframe lookback of 1, 7, 14, or 30 days.
The endpoint is part of x402scan, an analytics dashboard and block explorer for the x402 protocol built by Merit Systems. x402scan indexes on-chain x402 micropayment activity and exposes it through a suite of paid data endpoints. This particular endpoint costs $0.01 per request, payable via the x402 micropayment protocol. The address in the URL path (0x65c76a38593e1b98a522ede4c6f92aec14e04088) is a specific wallet; the general pattern is /api/x402/wallets/{address}/stats.
Note: During probing, this specific hardcoded-address URL returned 404 on both GET and POST. However, the OpenAPI spec documents the parameterized path /api/x402/wallets/{address}/stats as a live x402-protected endpoint. The 404 likely indicates the particular wallet address has no indexed data or the URL routing requires the /api/x402/ prefix rather than /api/data/. The broader x402scan origin is live (root returns 200) and the OpenAPI schema is well-documented.
Capabilities
Use cases
- —Retrieve aggregate payment statistics for a specific wallet participating in x402 micropayments
- —Monitor a wallet's x402 spending activity over configurable time windows (1, 7, 14, or 30 days)
- —Compare wallet activity across Base and Solana chains
- —Build dashboards tracking x402 protocol adoption per wallet
- —Audit an agent's cumulative x402 micropayment spend
Fit
Best for
- —Developers building analytics on top of the x402 micropayment ecosystem
- —AI agents that need to inspect their own or others' x402 spending history
- —Researchers studying x402 protocol adoption and transaction patterns
Not for
- —General-purpose blockchain explorers needing full transaction details (use the transactions endpoint instead)
- —Querying wallets outside the x402 payment ecosystem
- —Real-time streaming of wallet activity
Quick start
curl -X GET "https://www.x402scan.com/api/x402/wallets/0x65c76a38593e1b98a522ede4c6f92aec14e04088/stats?chain=base&timeframe=7" \
-H "X-Payment: <x402-payment-token>"Endpoint
Quality
The OpenAPI spec is thorough and documents the parameterized endpoint well with clear pricing ($0.01) and query parameters. However, the specific probed URL returned 404 (possibly wrong path prefix /api/data/ vs /api/x402/, or the wallet has no data), no response schema is documented, and no example responses are available from crawl material.
Warnings
- —Probed URL returned 404 on both GET and POST — the endpoint path in the listing (/api/data/wallets/...) may differ from the documented OpenAPI path (/api/x402/wallets/{address}/stats). Callers should use the /api/x402/ prefix.
- —No response schema is documented in the OpenAPI spec; response structure must be inferred.
- —No dedicated docs page exists (x402scan.com/docs returns 404).
Citations
- —Endpoint costs $0.01 per call via x402 micropaymenthttps://www.x402scan.com
- —Supports chain filter (base, solana) and timeframe filter (1, 7, 14, or 30 days)https://www.x402scan.com
- —x402scan is a payment data explorer and registry for the x402 protocol, built by Merit Systemshttps://www.x402scan.com
- —OpenAPI spec documents the endpoint as /api/x402/wallets/{address}/stats returning aggregate stats (tx count, total amount, unique recipients)https://www.x402scan.com