x402basequality 0.50

Paginated x402 payment transactions for a specific merchant address, $0.01 per call via x402.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint returns paginated USDC transfer records where a specific merchant (identified by their on-chain address) is the recipient, drawn from x402scan's indexed payment data. x402scan is a payment data explorer and registry for the x402 protocol, built by Merit Systems. It indexes x402 micropayment activity across Base and Solana chains.

The merchant transactions endpoint accepts query parameters for pagination (page, page_size up to 100), chain filtering (base or solana), timeframe lookback (1, 7, 14, or 30 days), and sorting by time or amount in ascending or descending order. Each call costs $0.01 USD, paid via the x402 protocol (X-Payment header). The endpoint is part of a broader suite of data endpoints on x402scan covering wallets, merchants, facilitators, resources, and a full-text search index.

Note: The specific URL in this listing uses the path `/api/data/merchants/{address}/transactions`, but the OpenAPI spec documents the canonical path as `/api/x402/merchants/{address}/transactions`. The probe returned 404 on the `/api/data/` variant, suggesting the endpoint may have been moved or renamed to the `/api/x402/` path. The `/api/x402/` variant is documented in the OpenAPI spec with full parameter definitions and x402 payment info.

Capabilities

merchant-transaction-historypaginated-resultschain-filteringtimeframe-filteringsort-by-timesort-by-amountx402-micropayment-auth

Use cases

  • Retrieve payment history for a specific x402 merchant address
  • Audit incoming USDC transfers to a merchant over a given timeframe
  • Analyze transaction volume and patterns for a merchant on Base or Solana
  • Build dashboards showing merchant payment activity in the x402 ecosystem

Fit

Best for

  • Agents or apps that need to query x402 payment flow data for a specific recipient
  • Analytics tools tracking merchant revenue in the x402 protocol
  • Developers building on x402 who need transaction-level visibility

Not for

  • Sending USDC (use the /api/x402/send endpoint instead)
  • Querying non-x402 on-chain transactions or general blockchain data
  • Free/unauthenticated bulk data access

Quick start

curl -H "X-Payment: <x402_payment_token>" \
  "https://www.x402scan.com/api/x402/merchants/0x4D37f28D2db99e8d35A6C725a5f1749A085850a3/transactions?page=0&page_size=10&sort_by=time&sort_order=desc"

Endpoint

Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.50/ 1.00

The OpenAPI spec is thorough with parameter definitions and pricing, but the specific /api/data/ URL path returned 404 on probe (likely moved to /api/x402/ path). No response schema or example responses are documented. No crawled docs page exists.

Warnings

  • The probed URL path /api/data/merchants/{address}/transactions returned 404; the OpenAPI spec documents the endpoint at /api/x402/merchants/{address}/transactions instead — the listing URL may be stale or renamed.
  • No response schema is provided in the OpenAPI spec — response structure must be inferred.
  • No dedicated documentation page was found (x402scan.com/docs returns 404).

Citations

Provenance

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

Agent access