Query x402 wallet transaction history — paginated transfers where a wallet is sender.
What it does
This endpoint is part of x402scan, a payment data explorer and registry for the x402 protocol built by Merit Systems. It returns paginated USDC transfer records where the specified wallet address is the sender, covering both Base and Solana chains. The endpoint supports filtering by chain (base or solana), timeframe lookback (1, 7, 14, or 30 days), and sorting by time or amount in ascending or descending order.
The specific URL listed here queries transactions for wallet address 0xCc0c538c651F64836fAcE59B9E1412995CEDE70E. According to the OpenAPI spec, the general pattern is /api/x402/wallets/{address}/transactions. Each call costs a fixed $0.01 micropayment via the x402 protocol. Results are paginated with configurable page size (1–100 items, default 10).
Note: The probe returned 404 for this specific wallet address endpoint, which may indicate the address has no indexed data or the URL path uses a different routing scheme than the OpenAPI-documented /api/x402/ prefix (the listed URL uses /api/data/ instead). The broader x402scan platform is live (root returns 200) and exposes a comprehensive OpenAPI spec covering wallets, merchants, facilitators, resources, and a USDC send endpoint.
Capabilities
Use cases
- —Retrieve outbound USDC transfer history for a specific wallet address
- —Audit x402 micropayment spending by an agent or user wallet
- —Analyze transaction patterns over configurable time windows (1–30 days)
- —Filter wallet activity by blockchain (Base vs Solana)
- —Sort and paginate through large transaction sets programmatically
Fit
Best for
- —Agents that need to audit their own x402 spending history
- —Analytics dashboards tracking x402 protocol payment flows
- —Developers building wallet activity views for x402-enabled applications
Not for
- —Querying non-x402 (general ERC-20) token transfers
- —Real-time streaming of transactions — this is a paginated polling endpoint
- —Wallets that have never participated in x402 payments
Quick start
curl -H 'X-Payment: <x402_payment_header>' \
'https://www.x402scan.com/api/x402/wallets/0xCc0c538c651F64836fAcE59B9E1412995CEDE70E/transactions?page=0&page_size=10&chain=base&sort_by=time&sort_order=desc'Endpoint
Quality
The OpenAPI spec is detailed with parameter definitions and pricing, but the specific endpoint URL probed (/api/data/wallets/...) returned 404 on both GET and POST. The documented path pattern uses /api/x402/wallets/{address}/transactions instead, suggesting a URL mismatch. No response schema or example responses are provided in the spec. No dedicated docs page exists.
Warnings
- —Probed endpoint URL uses /api/data/ path prefix but OpenAPI spec documents /api/x402/ prefix — the listed URL may be incorrect or deprecated
- —Probe returned 404 on both GET and POST — endpoint may not be live at this exact URL
- —No response schema is defined in the OpenAPI spec; response structure must be inferred
- —No dedicated documentation pages found (/docs, /api, /pricing all return 404)
Citations
- —The endpoint costs $0.01 per call via x402 micropaymenthttps://www.x402scan.com
- —Supports filtering by chain (base, solana), timeframe (1, 7, 14, 30 days), sorting by time or amounthttps://www.x402scan.com
- —x402scan is described as a payment data explorer and registry for the x402 protocolhttps://www.x402scan.com
- —Built by Merit Systemshttps://www.x402scan.com
- —Root page returns 200 and shows live ecosystem stats (97.43K transactions, $17.06K volume in past 24 hours)https://www.x402scan.com