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 as a path parameter, it returns metrics such as transaction count, total transfer amount, and unique recipients. Results 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 USDC transfers made via the x402 micropayment protocol across Base and Solana chains, tracking merchants, buyers, facilitators, and resources. The wallet stats endpoint costs $0.01 per request, paid via an x402 micropayment in the X-Payment header.

Note: the probe returned HTTP 404 for this specific wallet address (0xa9f39e1baf7aaafd990c99e360b2de1e2907ec65), which likely means this particular address has no indexed data rather than the endpoint being down. The broader x402scan origin is live (root returns 200) and the OpenAPI spec documents this endpoint pattern at /api/x402/wallets/{address}/stats with a 402 payment challenge. Other wallet addresses with actual x402 activity should return the expected 402 challenge and then data upon payment.

Capabilities

wallet-statsx402-micropaymentusdc-transfer-analyticschain-filtertimeframe-filterbase-chainsolana-chainpaginated-api

Use cases

  • Retrieve aggregate spending stats for a wallet that uses x402 micropayments
  • Monitor a wallet's x402 transaction count and volume over configurable timeframes
  • Compare wallet activity across Base and Solana chains
  • Build dashboards tracking x402 ecosystem participant behavior
  • Audit an agent wallet's cumulative x402 spending

Fit

Best for

  • Agents needing to inspect their own x402 spending history
  • Analytics tools monitoring x402 protocol adoption
  • Developers building x402 ecosystem dashboards
  • Wallet profiling for x402 buyer/sender addresses

Not for

  • General-purpose blockchain explorer queries outside x402 transfers
  • Looking up wallets with no x402 transaction history (returns 404)
  • Free/unauthenticated access — requires x402 micropayment per call

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.55/ 1.00

The OpenAPI spec is well-documented with clear parameters, pricing, and endpoint descriptions. However, the probe returned 404 for the specific address in the listing URL (likely no data for that address), no response schema is provided, and no example responses are available from the crawl. The endpoint pattern is clearly defined but response shape must be inferred.

Warnings

  • Probe returned 404 for the specific wallet address 0xa9f39e1baf7aaafd990c99e360b2de1e2907ec65 — this address likely has no indexed x402 data. The endpoint pattern itself is documented and expected to work for addresses with activity.
  • No response schema documented in the OpenAPI spec — the shape of the returned stats object is unknown.
  • No example responses available from crawl material.
  • The listing URL uses /api/data/wallets/ but the OpenAPI spec documents /api/x402/wallets/ — the actual canonical path may differ from the registered endpoint URL.

Citations

Provenance

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

Agent access