Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt retrieval API. The specific resource `/api/v1/transactions/230/receipt` returns receipt data for transaction ID 230 in JSON format. Payment is handled inline via the x402 protocol: callers attach an `X-PAYMENT` header with a USDC payment on the Base network. The maximum amount required per call is 20,000 base units of USDC (0.02 USD, i.e. two cents), consistent with the site-wide $0.02/request pricing.
The provider, lowpaymentfee.com, advertises a broader suite of pay-per-call APIs spanning data & analytics (metrics, reports, data export, insights), AI & ML (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, only the transaction receipt endpoint was probed and confirmed live.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available from the crawl. The x402 challenge confirms the endpoint is live and accepting POST requests, settling payments to address 0x1A2B…85F3 using USDC (contract 0x8335…2913) on Base. The output schema indicates HTTP POST with discoverable=true.
Capabilities
Use cases
- —Retrieving transaction receipt data for a specific transaction ID
- —Programmatic access to receipt records without API key management
- —Agent-driven workflows that need verifiable transaction receipts with inline crypto payment
Fit
Best for
- —Developers wanting keyless, pay-per-call access to transaction receipts
- —AI agents that can settle x402 payments in USDC on Base
- —Use cases requiring low-friction, no-subscription API access
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who cannot pay in USDC on the Base network
- —Applications requiring detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/230/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge confirms the endpoint is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request parameters, response schema, or what data the receipt actually contains. No OpenAPI spec, no examples, and all doc pages are empty wallet-connect stubs. This is effectively a stub listing.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
- —No OpenAPI or JSON schema describing request parameters or response format
- —Only one specific transaction ID (230) endpoint was probed; unclear if other IDs or the broader advertised API suite are functional
- —The broader suite of AI, analytics, finance, and utility endpoints listed on the homepage were not probed and cannot be confirmed live
Citations
- —The endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/230/receipt
- —maxAmountRequired is 20000 base units of USDC (0.02 USD) with asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/230/receipt
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The provider lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com