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 0x91b1cb898bc112f39fd6b102807759951292394f), it returns metrics such as transaction count, total transfer volume, and unique recipients. The data covers x402 protocol micropayments on both Base and Solana chains.
The endpoint is part of x402scan, a payment data explorer and analytics dashboard built by Merit Systems. It indexes on-chain x402 transfers and exposes them through a suite of paid API endpoints. Each call to this wallet stats endpoint costs $0.01 via an x402 micropayment (sent in the X-Payment header). Optional query parameters let you filter by chain (base or solana) and timeframe (1, 7, 14, or 30 days lookback).
Note: the probe returned HTTP 404 for this specific wallet address, which likely means the address has no indexed x402 activity rather than the endpoint being down. The broader x402scan API surface (documented via OpenAPI) is live, and the parameterized path /api/x402/wallets/{address}/stats is the canonical form. The endpoint URL hardcodes a specific address; callers should substitute their target wallet address in the path.
Capabilities
Use cases
- —Retrieve aggregate payment statistics for a wallet that sends x402 micropayments
- —Monitor a specific address's x402 spending activity over configurable time windows
- —Compare wallet activity across Base and Solana chains
- —Build dashboards tracking x402 protocol adoption per wallet
- —Audit an agent's cumulative x402 spend and recipient diversity
Fit
Best for
- —Agents or dashboards needing quick wallet-level x402 payment summaries
- —Developers building analytics on top of the x402 micropayment ecosystem
- —Monitoring spending patterns of AI agents using x402-gated APIs
Not for
- —General-purpose blockchain explorers (this only covers x402 protocol transfers)
- —Querying wallets with no x402 activity (returns 404)
- —Real-time streaming of individual transactions (use the transactions endpoint instead)
Quick start
curl -H "X-Payment: <x402_payment_token>" \
"https://www.x402scan.com/api/x402/wallets/0x91b1cb898bc112f39fd6b102807759951292394f/stats?chain=base&timeframe=30"Endpoint
Quality
Full OpenAPI schema with clear parameter definitions and pricing ($0.01/call). However, the specific hardcoded-address endpoint returned 404 during probing (likely no indexed data for that wallet), no response schema or example responses are documented, and no dedicated docs pages exist. The broader API surface appears live based on the landing page showing real-time stats.
Warnings
- —Probe returned 404 for this specific wallet address — the address likely has no indexed x402 activity; the parameterized endpoint /api/x402/wallets/{address}/stats is the canonical form
- —No response schema documented in the OpenAPI spec — response structure must be inferred
- —No dedicated documentation pages found (docs, pricing, README all return 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, 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
- —OpenAPI spec documents the wallets/{address}/stats endpoint with operationId x402_wallets_statshttps://www.x402scan.com