Transaction receipt retrieval via x402 micropayment on Base network, $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource path `/api/v1/transactions/397/receipt`) behind an x402 paywall. The provider operates a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) via the x402 "exact" scheme. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`. No API key or account registration is required — access is granted purely through the x402 payment header.
Documentation on the site is extremely thin: the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the receipt payload actually contains. The platform's landing page lists many endpoints across several domains but provides no technical detail beyond endpoint paths and pricing. Treat this listing as a stub until richer documentation becomes available.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID via micropayment
- —Programmatic access to receipt data without account registration
- —Agent-driven workflows that need on-demand transaction documentation
Fit
Best for
- —Agents or scripts that need one-off transaction receipt lookups
- —Developers exploring x402 payment-gated APIs on Base
- —Use cases where no-signup, pay-per-request access is preferred
Not for
- —Bulk or high-volume receipt retrieval (no documented batch endpoint)
- —Users who need detailed API documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/397/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof to access the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is virtually no documentation: no OpenAPI spec, no request/response schema, no explanation of what the receipt contains, and all doc pages render only 'Connect wallet'. The listing is effectively a stub.
Warnings
- —No OpenAPI or schema documentation available — response format is unknown.
- —All documentation pages (docs, pricing, API, README) render only a 'Connect wallet' prompt with no technical content.
- —The specific endpoint path includes a hardcoded transaction ID (397); it is unclear whether this is parameterized or fixed.
- —No information on what fields the receipt JSON contains or what inputs the POST body expects.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02.https://lowpaymentfee.com/api/v1/transactions/397/receipt
- —The platform lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categories, all priced at $0.02 per request.https://lowpaymentfee.com
- —The platform advertises no API keys, no rate limits, instant access, and settlement on the Base network.https://lowpaymentfee.com