x402basequality 0.55

Query paginated x402 wallet transactions (sender side) for any address, paid via x402 micropayment.

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://www.x402scan.com/api/data/wallets/0xd4c940ba609b7e3b0E05cAfFd042c3e9424bcd29/transactions

What it does

This endpoint is part of x402scan, a payment data explorer and analytics platform for the x402 protocol, built by Merit Systems. It returns paginated USDC transfer records where the specified wallet address acted as the sender. Results can be filtered by chain (Base or Solana), timeframe (1, 7, 14, or 30 days lookback), and sorted by time or amount in ascending or descending order. Pagination is 0-based with configurable page sizes from 1 to 100.

The endpoint is gated by an x402 micropayment of $0.01 per request. The broader x402scan API suite includes companion endpoints for merchant transactions, wallet/merchant aggregate stats, facilitator analytics, resource registry, full-text resource search, and a USDC send capability. All data endpoints cost $0.01–$0.02 each.

Note: the specific URL in this listing includes a hardcoded wallet address (0xd4c940ba609b7e3b0E05cAfFd042c3e9424bcd29) but the underlying API pattern is /api/x402/wallets/{address}/transactions, accepting any valid wallet address. The probe returned 404 rather than 402, which may indicate the hardcoded address has no indexed data or the endpoint path uses a different prefix (/api/x402/ vs /api/data/). The OpenAPI spec documents the canonical path as /api/x402/wallets/{address}/transactions.

Capabilities

wallet-transaction-historyx402-payment-gatedpaginationchain-filtertimeframe-filtersort-by-timesort-by-amountbase-chainsolana-chain

Use cases

  • —Retrieve outbound USDC transfer history for a specific wallet address on Base or Solana
  • —Audit x402 micropayment spending by an AI agent wallet over a given timeframe
  • —Build dashboards showing wallet-level x402 transaction activity
  • —Analyze spending patterns of x402 protocol participants

Fit

Best for

  • —Agents needing to audit their own x402 spending history
  • —Analytics tools tracking x402 ecosystem activity
  • —Developers building on the x402 protocol who need transaction data
  • —Wallet-level spend reporting across Base and Solana

Not for

  • —General-purpose blockchain explorers (covers only x402 USDC transfers, not all on-chain activity)
  • —Free/unauthenticated bulk data export (each page costs $0.01)
  • —Real-time streaming of transactions (polling-based, not websocket)

Quick start

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

Endpoint

URLhttps://www.x402scan.com/api/data/wallets/0xd4c940ba609b7e3b0E05cAfFd042c3e9424bcd29/transactions
Transporthttp
Protocolx402
Pay to0x2EC4545f96A24876764bF2B04D54E66A1351bE71
CurrencyUSD COIN

Quality

0.55/ 1.00

The OpenAPI spec is thorough with well-documented parameters, pricing, and multiple related endpoints. However, the probe returned 404 (not 402) on the listed URL, suggesting a path mismatch between /api/data/ and /api/x402/. No response schema or example responses are provided. No dedicated docs page exists.

Warnings

  • —Probe returned 404 on both GET and POST — the listed URL uses /api/data/wallets/... but the OpenAPI spec documents /api/x402/wallets/... — the canonical path is likely /api/x402/wallets/{address}/transactions
  • —No response schema documented in the OpenAPI spec — response structure must be inferred
  • —No example responses available from probe or crawl

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/EYw99q
Query paginated x402 wallet transactions (sender side) for any address, paid via x402 micropayment. — Clawmart · Clawmart