x402basequality 0.55

Aggregate wallet stats (tx count, volume, unique recipients) from the x402 protocol 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, it reports metrics such as transaction count, total transfer amount, and unique recipients. The data covers x402 protocol micropayments on both Base and Solana chains. 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 built by Merit Systems. x402scan indexes on-chain x402 transfers and exposes them through a suite of paid data endpoints. This particular wallet stats endpoint costs $0.01 per request, paid via the x402 micropayment protocol. The broader x402scan API also offers endpoints for merchant stats, transaction histories, facilitator analytics, resource search, and a registry for x402-protected resources.

Note: During probing, this endpoint returned HTTP 404 rather than the expected 402 payment challenge. The URL in the Bazaar listing uses the path `/api/data/wallets/{address}/stats`, but the OpenAPI spec documents the canonical path as `/api/x402/wallets/{address}/stats`. The endpoint is likely live at the `/api/x402/` path variant. Callers should use the OpenAPI-documented path instead.

Capabilities

wallet-statsx402-micropaymenttransaction-analyticsmulti-chain-querybase-chainsolana-chaintimeframe-filteraggregate-metrics

Use cases

  • Retrieve aggregate payment statistics for a specific wallet address participating in x402 micropayments
  • Monitor a wallet's x402 spending activity over configurable time windows (1, 7, 14, or 30 days)
  • Compare wallet activity across Base and Solana chains
  • Feed wallet-level metrics into dashboards or agent decision-making pipelines
  • Audit x402 protocol usage for a given sender address

Fit

Best for

  • Agents that need to look up x402 spending summaries for a wallet
  • Analytics dashboards tracking x402 ecosystem participation
  • Developers building on the x402 protocol who need sender-side metrics

Not for

  • General-purpose blockchain explorers needing full transaction details (use the transactions endpoint instead)
  • Querying wallets outside the x402 payment ecosystem
  • Free/unauthenticated access — every call requires a $0.01 x402 micropayment

Quick start

curl -X GET \
  'https://www.x402scan.com/api/x402/wallets/0xb4a5f03ac17bd917d16d9a4f77dea13681be4fa5/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 descriptions. However, the probed endpoint URL returned 404 (path mismatch between Bazaar listing and OpenAPI spec), no response schema is provided, and no example responses are available. The crawl yielded no dedicated docs page.

Warnings

  • The Bazaar listing URL uses /api/data/wallets/{address}/stats but the OpenAPI spec documents /api/x402/wallets/{address}/stats — the probe returned 404, suggesting the listing URL is incorrect.
  • No response schema is documented in the OpenAPI spec — the 200 response only says 'Successful response' with no body definition.
  • No example response data is available; the response structure must be inferred from the endpoint summary (tx count, total amount, unique recipients).

Citations

Provenance

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

Agent access