x402basequality 0.55

Aggregate wallet stats (tx count, volume, unique recipients) for any x402 address, $0.01 per call.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint returns aggregate statistics for a specific wallet address within the x402 payment ecosystem. Given a wallet address in the URL path, it returns metrics such as transaction count, total transfer amount, 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 x402 micropayment transfers across Base and Solana, tracking merchants, buyers, facilitators, and resources. The broader API suite includes endpoints for merchant stats, transaction histories, facilitator analytics, resource search, and a registry for x402-protected resources.

This specific endpoint costs $0.01 per call, paid via the x402 protocol (HTTP 402 challenge with X-Payment header). Note: the probe returned 404 rather than 402 for the specific hardcoded address in the listing URL, which may indicate the address has no indexed data or the URL path format differs from the OpenAPI spec (the spec uses `/api/x402/wallets/{address}/stats` while the listing URL uses `/api/data/wallets/{address}/stats`). The OpenAPI spec is well-documented with clear parameter definitions and pricing metadata.

Capabilities

wallet-statsx402-micropaymenton-chain-analyticsbase-chainsolana-chaintimeframe-filteraggregate-metricspaginated-api

Use cases

  • Retrieve aggregate payment statistics for a specific wallet address across x402 transactions
  • Monitor a wallet's x402 spending activity over configurable time windows (1, 7, 14, or 30 days)
  • Filter wallet stats by chain (Base or Solana) to analyze cross-chain payment behavior
  • Build dashboards tracking x402 protocol adoption by analyzing wallet-level metrics

Fit

Best for

  • Agents needing quick wallet-level summaries of x402 micropayment activity
  • Analytics tools monitoring x402 ecosystem participation
  • Developers building on the x402 protocol who need wallet intelligence

Not for

  • General-purpose blockchain explorers needing full transaction details (use the transactions endpoint instead)
  • Non-x402 token transfer analytics — this only covers x402-indexed USDC transfers
  • Free or unauthenticated access — every call requires a $0.01 x402 micropayment

Quick start

curl -H "X-Payment: <x402_payment_token>" \
  "https://www.x402scan.com/api/x402/wallets/0xc8c25a344c7043dd6cc6738e58629489b03ce6d3/stats?chain=base&timeframe=7"

Endpoint

Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.55/ 1.00

The OpenAPI spec is thorough with clear pricing, parameters, and endpoint descriptions. However, the probe returned 404 (not 402) suggesting a URL path mismatch between the listing URL (/api/data/wallets/...) and the spec (/api/x402/wallets/...). No response schema or example responses are documented. No crawled docs page exists.

Warnings

  • The listing URL uses path /api/data/wallets/{address}/stats but the OpenAPI spec defines /api/x402/wallets/{address}/stats — the endpoint may have been moved or the listing URL is incorrect.
  • Probe returned 404 on both GET and POST, which could indicate the specific address has no data or the path prefix is wrong.
  • No response schema is documented in the OpenAPI spec — response structure must be inferred.
  • No dedicated documentation page exists (x402scan.com/docs returns 404).

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 02:36:19Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access