x402basequality 0.55

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

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://www.x402scan.com/api/data/wallets/0x41719233c99e4f60c71f954f087b0e2e7624aa9e/stats

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 sent, 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 is parameterized with a particular wallet address (0x41719233c99e4f60c71f954f087b0e2e7624aa9e), but the same pattern applies to any wallet address substituted into the path.

Note: The probe returned 404 for this specific wallet address, which may indicate the address has no indexed activity or the endpoint requires the path prefix /api/x402/ rather than /api/data/. The OpenAPI spec documents the canonical path as /api/x402/wallets/{address}/stats. The broader x402scan platform is live (root returns 200) and the OpenAPI spec is well-documented with clear pricing and parameter definitions.

Capabilities

wallet-statsx402-micropaymentchain-filtertimeframe-filteraggregate-analyticsbase-chainsolana-chain

Use cases

  • —Retrieve aggregate sending statistics for a specific wallet address in the x402 ecosystem
  • —Monitor wallet activity over configurable time windows (1, 7, 14, or 30 days)
  • —Compare wallet behavior across Base and Solana chains
  • —Build dashboards tracking x402 protocol adoption by wallet

Fit

Best for

  • —Agents needing quick wallet-level summaries without paginating through individual transactions
  • —Analytics pipelines monitoring x402 protocol usage
  • —Developers building wallet profile pages for x402 participants

Not for

  • —Querying non-x402 on-chain transactions (only indexes x402 protocol transfers)
  • —Retrieving individual transaction details (use the wallets/{address}/transactions endpoint instead)
  • —Free or high-volume bulk data extraction (each call costs $0.01)

Quick start

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

Endpoint

URLhttps://www.x402scan.com/api/data/wallets/0x41719233c99e4f60c71f954f087b0e2e7624aa9e/stats
Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.55/ 1.00

The OpenAPI spec is thorough with clear pricing, parameters, and operation descriptions, but the probed endpoint returned 404 (possibly due to a path mismatch: /api/data/ vs /api/x402/). No response schema or example responses are documented. No crawled docs page exists.

Warnings

  • —Probe returned 404 on both GET and POST — the listed URL uses /api/data/wallets/ but the OpenAPI spec documents the path as /api/x402/wallets/{address}/stats. The canonical path may differ from the cataloged URL.
  • —No response schema is provided in the OpenAPI spec; the 200 response is described only as 'Successful response' with no body definition.
  • —No example response data is available from probe or documentation.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/T4Rqgj
Aggregate wallet stats (tx count, volume, unique recipients) from the x402 protocol explorer. — Clawmart · Clawmart