x402basequality 0.55

Aggregate stats for a specific x402 merchant address — volume, tx count, unique buyers.

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

What it does

This endpoint returns aggregate statistics for a specific merchant (payment recipient) in the x402 protocol ecosystem. Given a merchant wallet address, it returns metrics such as transaction count, total volume, and unique buyer count. The data 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 x402 micropayments across Base and Solana chains, tracking merchants, buyers, facilitators, and resources. All data query endpoints are themselves gated behind x402 micropayments.

This specific endpoint costs $0.01 per call, paid via the x402 protocol. Note that during probing the endpoint returned 404 rather than the expected 402 challenge — this may be because the URL path in the Bazaar listing uses a legacy `/api/data/merchants/` prefix while the OpenAPI spec documents the path as `/api/x402/merchants/{address}/stats`. The canonical path from the OpenAPI spec should be used instead.

Capabilities

merchant-statsx402-analyticsusdc-transfer-trackingchain-filteringtimeframe-filteringaggregate-metrics

Use cases

  • —Retrieve aggregate payment stats (volume, tx count, unique buyers) for a specific x402 merchant address
  • —Monitor merchant revenue trends over 1, 7, 14, or 30 day windows
  • —Compare merchant activity across Base and Solana chains
  • —Build dashboards tracking x402 ecosystem merchant performance
  • —Audit payment flows to a specific recipient wallet

Fit

Best for

  • —Agents that need to evaluate x402 merchant activity before transacting
  • —Analytics dashboards tracking x402 protocol adoption
  • —Developers building merchant-facing reporting tools

Not for

  • —Looking up non-x402 on-chain transfers or general blockchain data
  • —Sending payments (use the /api/x402/send endpoint instead)
  • —Real-time streaming transaction feeds

Quick start

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

Endpoint

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

Quality

0.55/ 1.00

Full OpenAPI schema with clear parameter definitions and pricing ($0.01/call). However, the probed endpoint URL returned 404 instead of 402, suggesting the Bazaar-listed path (/api/data/merchants/...) differs from the canonical OpenAPI path (/api/x402/merchants/.../stats). No response schema or example responses are documented. No dedicated docs page exists.

Warnings

  • —Probe returned 404 on both GET and POST — the Bazaar-listed URL uses /api/data/merchants/ but the OpenAPI spec documents /api/x402/merchants/{address}/stats. The canonical path may differ from the registered one.
  • —No response schema is documented in the OpenAPI spec; response structure must be inferred.
  • —No dedicated documentation pages found (/docs, /api, /pricing all return 404).

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/y9N36L
Aggregate stats for a specific x402 merchant address — volume, tx count, unique buyers. — Clawmart · Clawmart