x402basequality 0.65

Query x402 protocol wallet transactions, merchant stats, and resource registry via micropayment-gated API.

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. It indexes USDC transfers on Base and Solana that flow through x402-enabled endpoints, and exposes that data through a suite of REST API endpoints gated by x402 micropayments ($0.01–$0.02 per call).

This specific endpoint — `/api/x402/wallets/{address}/transactions` — returns a paginated list of x402 transfers where the specified wallet address is the sender. Results can be filtered by chain (Base or Solana), timeframe (1, 7, 14, or 30 days), and sorted by time or amount in ascending or descending order. Pagination supports up to 100 items per page. The endpoint costs $0.01 per request, paid via the x402 protocol.

The broader x402scan API also offers endpoints for merchant transaction history, wallet and merchant aggregate stats, facilitator analytics, a full-text resource search, and a resource registry where developers can register their own x402-protected endpoints. A send endpoint allows programmatic USDC transfers on Base or Solana with dynamic pricing. Registry write operations use SIWX (Sign-In With X) wallet authentication rather than micropayments.

Capabilities

wallet-transaction-historypaginated-resultschain-filtertimeframe-filtersort-by-timesort-by-amountx402-micropayment-authbase-chainsolana-chain

Use cases

  • Retrieve outbound USDC transfer history for a specific wallet address on Base or Solana
  • Monitor agent spending patterns across x402-enabled services
  • Build dashboards tracking x402 ecosystem payment flows
  • Audit wallet activity over configurable timeframes (1–30 days)
  • Integrate x402 transaction data into accounting or analytics pipelines

Fit

Best for

  • Developers building on the x402 protocol who need transaction visibility
  • AI agents that need to audit their own spending history
  • Analytics platforms tracking the x402 micropayment ecosystem

Not for

  • General-purpose blockchain explorers (only indexes x402 USDC transfers, not all on-chain activity)
  • Users needing free API access (every data call requires a $0.01 x402 micropayment)
  • Non-USDC token transfer lookups

Quick start

curl -H "X-Payment: <x402_payment_header>" \
  "https://www.x402scan.com/api/x402/wallets/0x6af92112b3f74BfC6e191a3a036908db13843883/transactions?page=0&page_size=10&chain=base&sort_by=time&sort_order=desc"

Example

Request

{
  "url": "https://www.x402scan.com/api/x402/wallets/0x6af92112b3f74BfC6e191a3a036908db13843883/transactions?page=0&page_size=10&chain=base&timeframe=7&sort_by=time&sort_order=desc",
  "method": "GET",
  "headers": {
    "X-Payment": "<x402_payment_token>"
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.65/ 1.00

The OpenAPI spec is thorough with clear parameter definitions and pricing info, but the specific endpoint URL probed returned 404 (likely because the path uses /api/data/wallets/ instead of the documented /api/x402/wallets/). No response schema examples are available, and no dedicated docs page exists. The broader API is well-documented via OpenAPI guidance.

Warnings

  • The probed URL path (/api/data/wallets/...) returned 404; the correct documented path appears to be /api/x402/wallets/{address}/transactions — the Bazaar record URL may be stale or incorrect.
  • No response body schema is defined in the OpenAPI spec — only '200: Successful response' without structure details.
  • No dedicated documentation page exists (x402scan.com/docs returns 404).

Citations

Provenance

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

Agent access