x402basequality 0.45

Aggregate wallet stats (tx count, volume, unique recipients) from the x402 payment ecosystem for $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 this case 0x31e46688ff3f568f0b290efc330c2d9a266ec21b), it provides metrics such as transaction count, total transfer volume, and unique recipients. It is part of x402scan, a payment data explorer and analytics platform built by Merit Systems that indexes x402 protocol activity across Base and Solana chains.

The endpoint accepts optional query parameters to filter by chain (base or solana) and timeframe (1, 7, 14, or 30 days lookback). It costs $0.01 per request, paid via the x402 micropayment protocol using USDC. The broader x402scan API suite includes endpoints for merchant stats, facilitator analytics, resource discovery, full-text search across registered x402 resources, and even a USDC send endpoint.

Note that the specific wallet address in this URL is hardcoded into the path. The underlying OpenAPI spec defines the general pattern as /api/x402/wallets/{address}/stats, meaning any valid wallet address can be substituted. The probe returned a 404 rather than the expected 402 challenge, which may indicate the specific address is not indexed or the endpoint path uses a different base path (/api/x402/ vs /api/data/). The OpenAPI spec lists the canonical path as /api/x402/wallets/{address}/stats, not /api/data/wallets/{address}/stats.

Capabilities

wallet-statsx402-micropaymentchain-filtertimeframe-filteraggregate-analyticsusdc-payment

Use cases

  • Retrieve aggregate payment statistics for a specific wallet address in the x402 ecosystem
  • Monitor wallet activity over configurable timeframes (1, 7, 14, or 30 days)
  • Filter wallet stats by chain (Base or Solana) to analyze cross-chain behavior
  • Build dashboards tracking x402 protocol adoption per wallet
  • Audit a wallet's x402 spending history programmatically

Fit

Best for

  • Agents needing quick aggregate stats on x402 wallet activity
  • Developers building analytics tools on top of the x402 protocol
  • Monitoring x402 payment volumes for specific addresses

Not for

  • General-purpose blockchain transaction lookups outside the x402 ecosystem
  • Querying non-USDC token transfers or DeFi activity
  • Real-time streaming of wallet events (this is a polling/request-response API)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.45/ 1.00

The OpenAPI spec is well-documented with clear parameter definitions and pricing, but the probed endpoint path (/api/data/wallets/...) returned 404 rather than the expected 402 challenge. The canonical path appears to be /api/x402/wallets/{address}/stats per the spec. No response schema or example responses are provided. No dedicated docs page exists.

Warnings

  • Probe returned 404 on both GET and POST — the listed endpoint path /api/data/wallets/{address}/stats does not match the OpenAPI canonical path /api/x402/wallets/{address}/stats. The correct base path is likely /api/x402/.
  • No response schema is documented in the OpenAPI spec; response structure must be inferred.
  • No dedicated documentation page found (/docs, /api, /pricing all return 404).

Citations

Provenance

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

Agent access

Aggregate wallet stats (tx count, volume, unique recipients) from the x402 payment ecosystem for $0.01 per call. — Clawmart · Clawmart