x402basequality 0.50

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. Given a wallet address, it reports metrics such as transaction count, total transfer amount, and unique recipients. The data is sourced from x402scan, a payment data explorer and block explorer for the x402 protocol, built by Merit Systems. The endpoint supports optional query parameters to filter by chain (Base or Solana) and timeframe (1, 7, 14, or 30 days lookback).

The endpoint is part of a broader x402scan API suite that indexes x402 micropayment activity across Base and Solana chains. Other sibling endpoints cover merchant stats, buyer rankings, facilitator analytics, resource registry, and full-text search. All data endpoints cost $0.01 per call via x402 micropayment, paid in USDC. The wallet address in the URL path (0x3c3d…4489) is a specific address; the same endpoint pattern works for any wallet address by substituting the path parameter.

Note: During probing, this specific URL returned 404 on both GET and POST. The OpenAPI spec defines the parameterized route at `/api/x402/wallets/{address}/stats` which should return 402 for valid addresses. The 404 may indicate the particular address has no indexed data, or the endpoint requires the canonical `/api/x402/` path prefix rather than `/api/data/`. The listing URL uses `/api/data/wallets/` while the OpenAPI spec documents `/api/x402/wallets/`. Callers should use the `/api/x402/wallets/{address}/stats` path.

Capabilities

wallet-statsx402-micropaymenttransaction-analyticschain-filtertimeframe-filterbase-chainsolana-chainaggregate-metrics

Use cases

  • Retrieve aggregate payment statistics for a specific wallet address on Base or Solana
  • Monitor a wallet's x402 micropayment activity over configurable time windows
  • Build dashboards showing wallet-level transaction counts, volumes, and unique counterparties
  • Audit x402 protocol spending for a given sender address

Fit

Best for

  • Agents needing quick wallet-level x402 payment summaries
  • Analytics dashboards tracking x402 ecosystem activity
  • Developers building on the x402 micropayment protocol

Not for

  • General-purpose blockchain data (non-x402 transactions are not indexed)
  • Real-time streaming transaction feeds (this returns aggregate snapshots)
  • Wallets or chains outside Base and Solana

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.50/ 1.00

The OpenAPI spec is well-documented with clear parameter definitions and pricing, but the probed endpoint returned 404 (possibly due to a path mismatch between /api/data/ and /api/x402/). No response schema or example responses are provided. No dedicated docs page exists.

Warnings

  • Probe returned 404 on both GET and POST — the listing URL uses /api/data/wallets/ but the OpenAPI spec documents /api/x402/wallets/. The canonical path may differ.
  • No response schema is documented in the OpenAPI spec; response structure must be inferred.
  • No dedicated documentation pages were found (/docs, /api, /pricing all return 404).

Citations

Provenance

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

Agent access