Paginated x402 wallet transaction history — outbound transfers for any address on Base or Solana.
What it does
This endpoint returns paginated outbound (sender-side) transfer records for a given wallet address within the x402 payment ecosystem. It is part of x402scan, a payment data explorer and analytics platform for the x402 protocol, built by Merit Systems. The endpoint is located at `/api/x402/wallets/{address}/transactions` and accepts query parameters for pagination (page, page_size), 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 micropayment protocol (X-Payment header). The specific URL listed here has the address `0xD12d26DE05d5Ee5965569C513c4B6A0f39d95f8A` hardcoded in the path, but the underlying OpenAPI spec defines this as a parameterized `{address}` path. The endpoint supports Base and Solana chains. Note that the probe returned 404 for this specific address, which may indicate the address has no indexed data or the endpoint requires a valid x402 payment header to resolve properly — the broader x402scan origin is live (HTTP 200 on root).
The x402scan platform indexes x402 payment activity across the ecosystem, tracking transactions, merchants, buyers, facilitators, and registered resources. The dashboard shows significant activity: roughly 97K transactions and $17K in volume in the past 24 hours at time of crawl, with facilitators including Coinbase, PayAI, and Meridian.
Capabilities
Use cases
- —Retrieve outbound x402 payment history for a specific wallet address
- —Audit agent spending by querying all transfers sent from a wallet
- —Analyze wallet activity over configurable time windows (1, 7, 14, or 30 days)
- —Filter and sort wallet transactions by chain, amount, or recency
- —Build dashboards tracking x402 protocol payment flows
Fit
Best for
- —Agents needing to audit their own x402 spending history
- —Developers building analytics on x402 payment activity
- —Monitoring outbound USDC transfers from a specific wallet on Base or Solana
Not for
- —Looking up arbitrary ERC-20 or SPL token transfers outside the x402 ecosystem
- —Real-time transaction streaming or webhooks
- —Querying inbound (merchant-side) transactions — use the merchants endpoint instead
Quick start
curl -H "X-Payment: <x402_payment_token>" \
"https://www.x402scan.com/api/x402/wallets/0xD12d26DE05d5Ee5965569C513c4B6A0f39d95f8A/transactions?page=0&page_size=10&chain=base&sort_by=time&sort_order=desc"Endpoint
Quality
The OpenAPI spec is well-documented with clear parameter definitions and pricing info, but the specific probed URL returned 404 (not a 402 challenge), no response schema is defined, and no example responses are available. The endpoint is likely functional behind a valid x402 payment but liveness could not be confirmed for this particular address.
Warnings
- —Probe returned 404 for both GET and POST on this specific wallet address — the endpoint may require a valid x402 payment header or the address may have no indexed data.
- —No response schema defined in the OpenAPI spec — response structure must be inferred.
- —No example responses available from docs or crawl.
- —The listed URL hardcodes a specific wallet address; the general parameterized endpoint is /api/x402/wallets/{address}/transactions.
Citations
- —Endpoint costs $0.01 USD per call via x402 micropaymenthttps://www.x402scan.com
- —Supports filtering by chain (base, solana), timeframe (1, 7, 14, 30 days), and sorting by time or amounthttps://www.x402scan.com
- —x402scan is described as a payment data explorer and registry for the x402 protocol, built by Merit Systemshttps://www.x402scan.com
- —Dashboard shows ~97K transactions and ~$17K volume in past 24 hourshttps://www.x402scan.com
- —Facilitators include Coinbase, PayAI, and Meridianhttps://www.x402scan.com