Retrieve x402 transaction history for a specific merchant address via x402scan's analytics API.
What it does
This endpoint returns transaction data for a specific merchant (seller) address on the x402scan platform — an analytics dashboard and block explorer for the x402 payment protocol ecosystem. The merchant address in the URL (0xf7b1...d57) identifies the seller whose transaction records are being queried.
The x402scan platform tracks the broader x402 ecosystem, reporting metrics such as transaction counts, volume, buyer/seller counts, and facilitator breakdowns across chains like Base and Solana. The endpoint itself is gated behind an x402 payment challenge (HTTP 402), meaning callers must complete a micropayment to access the data. However, the probe returned an empty challenge object, so the specific payment terms (token, amount, chain) are unknown.
Documentation for this API is not publicly available — the /docs, /api, /pricing, and /README paths all return 404. There is no OpenAPI spec or AI plugin manifest. The endpoint appears to be part of a Vercel-hosted preview deployment (indicated by the deployment hash in the subdomain). The canonical production domain appears to be x402scan.com based on the sitemap reference in robots.txt.
Capabilities
Use cases
- —Querying transaction history for a specific x402 merchant address
- —Monitoring payment volume and activity for an x402 seller
- —Building dashboards that aggregate x402 ecosystem payment data
- —Auditing x402 micropayment flows for a given address
Fit
Best for
- —Developers building on the x402 payment protocol who need transaction analytics
- —Merchants wanting programmatic access to their x402 payment history
- —Analytics tools tracking x402 ecosystem activity
Not for
- —General-purpose blockchain explorers (this is x402-specific)
- —Users needing free, unauthenticated access to transaction data
Quick start
curl -i https://x402scan-j55w7ornb-merit-systems.vercel.app/api/data/merchants/0xf7b1356cfed0eebe01d76da7ba9e9f8bf12d9d57/transactionsEndpoint
Quality
The endpoint is live (returns 402) but the challenge object is empty, providing no payment details. There is no OpenAPI spec, no documentation, no response schema, and no examples. The URL appears to be a Vercel preview deployment rather than a stable production endpoint.
Warnings
- —Empty x402 challenge: no payment terms (token, amount, chain, facilitator) were returned, making it impossible to determine pricing or how to pay.
- —No API documentation available — /docs, /api, /pricing, /README all return 404.
- —URL appears to be a Vercel preview deployment (contains deployment hash), not a stable production URL. The canonical domain may be x402scan.com.
- —No response schema or example responses available; the shape of returned transaction data is unknown.
Citations
- —x402scan describes itself as 'The x402 analytics dashboard and block explorer'https://x402scan-j55w7ornb-merit-systems.vercel.app
- —The sitemap in robots.txt references x402scan.com as the canonical domainhttps://x402scan-j55w7ornb-merit-systems.vercel.app
- —The endpoint returns HTTP 402 with an empty challenge objecthttps://x402scan-j55w7ornb-merit-systems.vercel.app/api/data/merchants/0xf7b1356cfed0eebe01d76da7ba9e9f8bf12d9d57/transactions
- —x402scan tracks ecosystem stats including ~89.68K transactions and ~$424.55K volume in 24 hourshttps://x402scan-j55w7ornb-merit-systems.vercel.app