Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt retrieval service. The specific resource `/api/v1/transactions/156/receipt` returns a receipt for transaction 156 in JSON format, payable per-call with USDC on the Base network. The x402 challenge confirms the endpoint is live and accepts exact-scheme payments.
The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (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. Payments settle in USDC on the Base network.
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 specific endpoint probed here (`/transactions/156/receipt`) is not listed on the homepage's API catalog, suggesting it may be an internal or unlisted resource. The x402 challenge confirms it is live and priced at 20,000 base units of USDC (6 decimals), which equals $0.02.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Integrating pay-per-request data access into agent workflows without API key management
- —Accessing financial or utility APIs with crypto micropayments on Base
Fit
Best for
- —Agents or applications that need keyless, pay-per-call API access
- —Developers wanting to test x402 payment flows on Base
- —Use cases requiring low-friction micropayment-gated endpoints
Not for
- —Production workloads requiring documented request/response schemas and SLAs
- —Users who need fiat payment options or cannot transact in USDC on Base
- —High-volume batch processing where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/156/receipt
# Returns 402 with x402 payment challenge; attach X-PAYMENT header with signed USDC payment on Base to access.Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the specific endpoint path (/transactions/156/receipt) is not listed in the site's public API catalog. Effectively a stub listing.
Warnings
- —No OpenAPI spec or schema documentation available
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The specific endpoint /api/v1/transactions/156/receipt is not listed in the site's public API catalog — may be unlisted or internal
- —No request body schema or response schema documented anywhere
- —Cannot verify what data the endpoint actually returns beyond the description 'Premium API Access'
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x8335…) on Base network, equaling $0.02https://lowpaymentfee.com/api/v1/transactions/156/receipt
- —All endpoints listed at $0.02/request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com