x402basequality 0.45

Aggregate wallet stats (tx count, volume, unique recipients) from the x402 protocol explorer.

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. It is part of x402scan, a payment data explorer and analytics dashboard for the x402 protocol, built by Merit Systems. The wallet stats endpoint provides metrics such as transaction count, total amount transferred, and unique recipients for any wallet that has participated as a sender in x402 transfers on Base or Solana.

The endpoint accepts optional query parameters to filter by chain (base or solana) and timeframe (1, 7, 14, or 30 days lookback). It is a GET request that costs $0.01 per call, paid via the x402 micropayment protocol. The specific URL listed here has the wallet address `0xd3720cada8d9b0352deedf78a62f579fcd011b64` hardcoded in the path, but the same pattern works for any wallet address at `/api/x402/wallets/{address}/stats`.

Note: The probe returned a 404 for this specific wallet address on both GET and POST, which may indicate the address has no indexed data or the endpoint path uses a different base path (`/api/x402/wallets/` rather than `/api/data/wallets/`). The OpenAPI spec documents the endpoint at `/api/x402/wallets/{address}/stats`, not `/api/data/wallets/{address}/stats`. The listed URL may be outdated or incorrect. x402scan is part of a broader suite of data endpoints covering merchants, facilitators, buyers, resources, and a resource registry.

Capabilities

wallet-statsx402-micropaymenttransaction-analyticschain-filtertimeframe-filteraggregate-metricsbase-chainsolana-chain

Use cases

  • Retrieve aggregate spending stats for a wallet participating in x402 payments
  • Monitor transaction volume and unique recipient counts for a specific sender address
  • Filter wallet activity by chain (Base or Solana) and time window
  • Build dashboards tracking x402 protocol adoption per wallet
  • Audit agent spending behavior across x402-enabled services

Fit

Best for

  • Agents that need to inspect their own x402 spending history
  • Analytics tools tracking x402 protocol usage
  • Developers building on the x402 payment ecosystem

Not for

  • General-purpose blockchain explorers (covers only x402 transfers, not all on-chain activity)
  • Wallets that have never participated in x402 payments
  • Free-tier usage — every call costs $0.01 via x402 micropayment

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.45/ 1.00

The OpenAPI spec is thorough and documents the endpoint pattern clearly at /api/x402/wallets/{address}/stats with pricing info. However, the actual listed URL uses /api/data/wallets/ which returned 404 on probe, suggesting the URL may be incorrect or deprecated. No response schema or example responses are documented. No dedicated docs page exists.

Warnings

  • The listed endpoint URL (/api/data/wallets/{address}/stats) returned 404; the OpenAPI spec documents the path as /api/x402/wallets/{address}/stats — the listing URL may be wrong.
  • No response schema is provided in the OpenAPI spec — response structure must be inferred.
  • No example responses or dedicated documentation pages are available.

Citations

Provenance

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

Agent access