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 access to a transaction receipt resource (transaction ID 357) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme. The cost per call is 20,000 base units of USDC, which equals $0.02 (two cents) given USDC's 6-decimal precision.
The provider's landing page advertises a broader suite of 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 required. However, the specific endpoint being listed here is a transaction receipt resource under `/api/v1/transactions/357/receipt`.
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 example payloads available. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the actual response format and fields of the receipt are unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 357 via programmatic pay-per-call access
- —Integrating x402 payment flows into agent-based workflows on the Base network
- —Demonstrating x402 protocol usage with USDC micropayments
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing pay-per-call access without API key management
- —Low-cost per-request access to transaction data
Not for
- —Production use cases requiring documented request/response schemas
- —Bulk or high-volume transaction data retrieval where per-call pricing is inefficient
- —Users who need detailed API documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/357/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof on Base to access.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming pricing and network details. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the specific resource (transaction 357 receipt) is not explained anywhere on the site. The listing is effectively a stub.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all render only 'Connect wallet'
- —No OpenAPI or output schema describing the receipt response format
- —The endpoint is for a specific transaction ID (357); it is unclear whether other transaction IDs are supported or what the receipt contains
- —The broader API suite advertised on the landing page is not verified — only this single endpoint was probed
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 USDC base units on the Base networkhttps://lowpaymentfee.com/api/v1/transactions/357/receipt
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/357/receipt
- —All endpoints listed at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider advertises APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com