Aggregate wallet stats (tx count, volume, unique recipients) from the x402 protocol ecosystem.
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 micropayments on both Base and Solana chains, and can be filtered by chain and by timeframe (1, 7, 14, or 30 days lookback).
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 payment transfers and exposes them through a suite of paid data endpoints. This particular wallet stats endpoint costs $0.01 per call, paid via the x402 micropayment protocol. The broader x402scan API also offers endpoints for merchant stats, transaction histories, facilitator analytics, resource registry lookups, full-text resource search, and even USDC sends.
Note: During probing, this specific endpoint returned HTTP 404 rather than the expected 402 challenge. The URL contains a hardcoded wallet address that may not exist in the index, or the endpoint path may use a different URL pattern than the one registered. The canonical OpenAPI path is `/api/x402/wallets/{address}/stats`, but the registered URL uses `/api/data/wallets/{address}/stats` — the `/data/` segment does not match the OpenAPI spec. The endpoint at the correct OpenAPI path is likely live given the rest of the API surface appears healthy (root returns 200, OpenAPI is well-formed).
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
- —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 x402 protocol usage
- —AI agents that need to monitor their own x402 spending
- —Researchers studying micropayment adoption on Base and Solana
Not for
- —General-purpose blockchain explorers needing full EVM/Solana transaction data beyond x402
- —Wallets that have never participated in x402 protocol payments
Quick start
curl -H "X-Payment: <x402-payment-header>" \
"https://www.x402scan.com/api/x402/wallets/0xb0f917c72c14ea7ff7f3e06d032f9959c96bf12c/stats?chain=base&timeframe=30"Endpoint
Quality
The OpenAPI spec is detailed with clear parameter definitions and pricing, but the registered endpoint URL (/api/data/wallets/...) does not match the OpenAPI path (/api/x402/wallets/...) and returned 404 on probe. No response schema or example responses are documented. The endpoint is likely functional at the correct path but the registered URL appears incorrect.
Warnings
- —Registered endpoint URL uses /api/data/ but OpenAPI spec defines /api/x402/ — the probed URL returned 404, suggesting a URL mismatch.
- —No response schema is documented in the OpenAPI spec — response structure must be inferred.
- —No example responses available from probe or documentation.
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 supports chain (base, solana) and timeframe (1, 7, 14, 30 days) query parametershttps://www.x402scan.com
- —The OpenAPI canonical path is /api/x402/wallets/{address}/statshttps://www.x402scan.com