Aggregate wallet stats (tx count, volume, unique recipients) for any x402 address, $0.01 per call.
What it does
This endpoint returns aggregate statistics for a specific wallet address within the x402 payment ecosystem. Given the wallet address `0x673fee2a5afee25df19f07ee644eafd4d2cd486e`, it returns metrics such as transaction count, total transfer volume, and unique recipients. The data can be filtered by chain (Base or Solana) and by timeframe (1, 7, 14, or 30 days lookback).
The endpoint is part of x402scan, a payment data explorer and analytics dashboard for the x402 protocol, built by Merit Systems. x402scan indexes on-chain USDC transfers made through x402-compatible facilitators (Coinbase, PayAI, Meridian, and others) across Base and Solana. All data query endpoints are themselves x402-gated, requiring a micropayment of $0.01 per call via the X-Payment header.
Note: The probe returned 404 for this specific wallet address path, which may indicate the URL uses a legacy routing pattern (`/api/data/wallets/...` vs. the documented `/api/x402/wallets/...`). The canonical OpenAPI spec documents the equivalent endpoint at `/api/x402/wallets/{address}/stats`. Callers should prefer the `/api/x402/` prefix. The broader x402scan origin is live (HTTP 200) and serves a full OpenAPI 3.1.0 specification.
Capabilities
Use cases
- —Retrieve aggregate payment statistics for a specific wallet address participating in x402 transfers
- —Monitor a wallet's x402 spending activity over configurable time windows (1, 7, 14, or 30 days)
- —Build dashboards tracking x402 ecosystem participation by wallet
- —Compare wallet activity across Base and Solana chains
Fit
Best for
- —Agents that need to look up x402 payment activity for a given wallet
- —Analytics pipelines monitoring the x402 micropayment ecosystem
- —Developers building on top of x402 who want spending summaries
Not for
- —General-purpose blockchain explorers needing full transaction detail beyond x402 transfers
- —Querying wallets on chains other than Base or Solana
Quick start
curl -H "X-Payment: <x402_payment_token>" \
"https://www.x402scan.com/api/x402/wallets/0x673fee2a5afee25df19f07ee644eafd4d2cd486e/stats?chain=base&timeframe=7"Endpoint
Quality
A full OpenAPI 3.1.0 spec with clear pricing and parameter definitions is available, but the specific probed URL (/api/data/wallets/…) returned 404 rather than 402, suggesting a legacy or incorrect path. No response schema or example response is documented. The canonical path is /api/x402/wallets/{address}/stats.
Warnings
- —Probed endpoint path /api/data/wallets/.../stats returned 404; the documented canonical path is /api/x402/wallets/{address}/stats — callers should use the /api/x402/ prefix.
- —No response schema or example response is provided in the OpenAPI spec for any endpoint.
- —No dedicated docs page found (https://www.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
- —Supports chain filter (base, solana) and timeframe filter (1, 7, 14, or 30 days)https://www.x402scan.com
- —x402scan is built by Merit Systemshttps://www.x402scan.com
- —The OpenAPI spec documents the canonical path as /api/x402/wallets/{address}/statshttps://www.x402scan.com