Aggregate wallet stats (tx count, volume, unique recipients) from the x402 payment 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 (in this case 0x11352f0bf719ccb77605a1e5e63af6e023ff3278), it provides metrics such as transaction count, total transfer volume, and unique recipients. The data covers x402 micropayment transfers on Base and Solana chains.
The endpoint is part of x402scan, a payment data explorer and analytics dashboard built by Merit Systems. x402scan indexes on-chain x402 protocol transfers and exposes them through a suite of paid API endpoints. This particular wallet stats endpoint accepts optional query parameters for chain filtering (base or solana) and timeframe lookback (1, 7, 14, or 30 days). It costs $0.01 per request, paid via the x402 micropayment protocol.
Note: The probe returned 404 for this specific wallet address on both GET and POST, which likely means the queried address has no indexed data rather than the endpoint being down. The broader x402scan origin is live (HTTP 200), and the OpenAPI spec documents this endpoint pattern at /api/x402/wallets/{address}/stats. Other wallet addresses with indexed activity should return a 402 challenge as expected.
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 ecosystem participant behavior
- —Audit an agent wallet'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 payment flows
Not for
- —General-purpose blockchain explorers needing full transaction details (use the transactions endpoint instead)
- —Querying wallets that have never participated in x402 transfers
- —Non-x402 ERC-20 or native token transfer analytics
Quick start
curl -H "X-Payment: <x402-payment-header>" \
"https://www.x402scan.com/api/data/wallets/0xYOUR_ADDRESS/stats?chain=base&timeframe=7"Endpoint
Quality
The OpenAPI spec is well-documented with clear parameter definitions and pricing, but the specific probed URL returned 404 (likely due to the hardcoded address having no indexed data). No response schema or example responses are provided. No dedicated docs page exists.
Warnings
- —Probe returned 404 for this specific wallet address — the address may have no indexed x402 activity. The endpoint pattern itself is documented in the OpenAPI spec and likely works for addresses with data.
- —The endpoint URL contains a hardcoded wallet address; callers should substitute their own address in the {address} path parameter.
- —No response schema is documented in the OpenAPI spec — response structure must be inferred at runtime.
- —No dedicated documentation page found (x402scan.com/docs returns 404).
Citations
- —The endpoint costs $0.01 per call via x402 micropaymenthttps://www.x402scan.com
- —x402scan is described as a payment data explorer and registry for the x402 protocol, built by Merit Systemshttps://www.x402scan.com
- —Wallet stats endpoint accepts chain (base/solana) and timeframe (1,7,14,30 days) query parametershttps://www.x402scan.com
- —The endpoint summary is 'Aggregate stats for a wallet (tx count, total amount, unique recipients)'https://www.x402scan.com