x402basequality 0.72

Query x402 protocol payment analytics: merchants, wallets, facilitators, and resources for $0.01/call.

Price
per_call
Protocol
x402
Verified
no

What it does

x402scan is a payment data explorer and registry for the x402 protocol, built by Merit Systems. This specific endpoint (`/api/x402/merchants`) returns a paginated list of merchants (top recipients by volume) in the x402 ecosystem. It supports filtering by chain (Base or Solana), timeframe (1, 7, 14, or 30 days), and sorting by volume, transaction count, or unique buyers. The endpoint costs $0.01 per call via x402 micropayment.

x402scan exposes a broader suite of data endpoints covering wallet transactions and stats, merchant transactions and stats, facilitator analytics, resource listings, and full-text resource search — all priced at $0.01–$0.02 each. There is also a registry system (requiring SIWX wallet authentication) for registering individual x402 resources or discovering all resources from an origin, plus a send endpoint for transferring USDC on Base or Solana with dynamic pricing up to $1,000.

The service indexes real ecosystem activity. At the time of crawl, the dashboard showed approximately 97.4K transactions and $17K in volume over the past 24 hours across 269 sellers and 10.2K buyers, with facilitators including Coinbase, PayAI, and Meridian. All data endpoints are paginated (up to 100 items per page) and accessible via standard GET requests with an X-Payment header.

Capabilities

x402-micropaymentmerchant-leaderboardwallet-analyticstransaction-historyfacilitator-statsresource-registryfull-text-searchusdc-transferbase-chainsolana-chainpaginationchain-filteringtimeframe-filtering

Use cases

  • Retrieve top x402 merchants ranked by payment volume, transaction count, or unique buyers
  • Monitor x402 ecosystem activity across Base and Solana chains
  • Look up aggregate stats and transaction history for specific wallets or merchants
  • Search the x402 resource registry to discover available paid endpoints
  • Send USDC programmatically to addresses on Base or Solana

Fit

Best for

  • AI agents needing to discover and evaluate x402-enabled API endpoints
  • Developers building dashboards or analytics on top of x402 payment data
  • Researchers analyzing micropayment ecosystem adoption and merchant activity

Not for

  • General-purpose blockchain exploration beyond x402 USDC transfers
  • Users who need free/unauthenticated access to payment data
  • Non-USDC token analytics

Quick start

curl -X GET "https://www.x402scan.com/api/x402/merchants?page=0&page_size=10&sort_by=volume&timeframe=7" \
  -H "X-Payment: <x402-payment-token>"

Example

Request

{
  "url": "https://www.x402scan.com/api/x402/merchants?page=0&page_size=10&chain=base&timeframe=7&sort_by=volume",
  "method": "GET",
  "headers": {
    "X-Payment": "<x402-payment-token>"
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.72/ 1.00

Full OpenAPI 3.1 schema with clear parameter definitions, pricing info, and endpoint descriptions. The probe returned 404 on the specific /api/data/merchants path (the listing URL uses /api/data/ but the OpenAPI spec uses /api/x402/), suggesting the listed endpoint URL may be slightly wrong or an alias. No response schema examples are provided. Ecosystem dashboard confirms live activity.

Warnings

  • The probe returned 404 on /api/data/merchants — the OpenAPI spec defines the endpoint at /api/x402/merchants instead. The listing URL may be incorrect.
  • No response body schema or example responses are documented in the OpenAPI spec.
  • Dedicated docs, pricing, and API pages all return 404; documentation is only available via the OpenAPI spec itself.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 01:18:27Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access