Query x402 wallet transaction history — paginated transfers where a wallet is the sender.
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 is the sender. The data covers transactions on both Base and Solana chains.
The 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 micropayment protocol (X-Payment header). The specific URL listed here has the address 0xF8eF78f84853dDBc30ba6cD75177A935Bc07131d hardcoded in the path.
Note: The probe returned 404 for this specific wallet address path, which may indicate the address has no indexed data or the endpoint routes differently than expected. However, the OpenAPI spec confirms the parameterized route /api/x402/wallets/{address}/transactions is a documented, live endpoint on x402scan. The broader x402scan origin returned HTTP 200 and the OpenAPI schema is fully published.
Capabilities
Use cases
- —Retrieve outbound USDC transfer history for a specific wallet address
- —Audit x402 protocol spending by a particular sender
- —Analyze transaction patterns over configurable time windows (1–30 days)
- —Filter and sort wallet payment activity by chain, amount, or recency
- —Build dashboards tracking agent or user spending across x402 endpoints
Fit
Best for
- —Agents needing to inspect their own x402 spending history
- —Analytics tools monitoring x402 ecosystem payment flows
- —Developers building wallet-level transaction audit UIs
- —Researchers studying micropayment patterns on Base and Solana
Not for
- —Looking up transactions where the wallet is the recipient (use merchants/{address}/transactions instead)
- —Free or unauthenticated access — requires x402 micropayment per call
- —Non-x402 blockchain transaction lookups (only indexes x402 protocol transfers)
Quick start
curl -H "X-Payment: <x402_payment_token>" \
"https://www.x402scan.com/api/x402/wallets/0xF8eF78f84853dDBc30ba6cD75177A935Bc07131d/transactions?page=0&page_size=10&chain=base&sort_by=time&sort_order=desc"Endpoint
Quality
The OpenAPI spec is well-documented with clear parameters, pricing ($0.01/call), and operation descriptions. However, the probe returned 404 for this specific hardcoded address path (possibly no indexed data for that wallet), no response schema is defined, and no example responses are available from the crawl.
Warnings
- —Probe returned 404 for this specific wallet address — the address may have no indexed x402 data, or the endpoint may only respond to known wallets.
- —No response schema defined in the OpenAPI spec — the shape of returned transaction objects is unknown.
- —No example responses available from crawl or docs (docs page returns 404).
Citations
- —Endpoint is documented as GET /api/x402/wallets/{address}/transactions returning paginated transfers where wallet is sender, costing $0.01 per callhttps://www.x402scan.com
- —x402scan is described as a payment data explorer and registry for the x402 protocol, built by Merit Systemshttps://www.x402scan.com
- —Supports filtering by chain (base, solana), timeframe (1, 7, 14, 30 days), and sorting by time or amounthttps://www.x402scan.com
- —The x402scan homepage shows live ecosystem stats: ~97K transactions, ~$17K volume, ~10K buyers in past 24 hourshttps://www.x402scan.com