x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 237) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per call, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/237/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The platform advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /README) appear to require a wallet connection and contain no substantive content in the crawl. There is no OpenAPI schema, no detailed request/response documentation, and no examples of what the receipt payload actually contains. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what data is returned or what inputs are expected beyond the POST method.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 237 via a single micropayment
- —Integrating pay-per-request APIs without managing API keys or subscriptions
- —Agent-driven workflows that need on-chain-settled API access
Fit
Best for
- —Developers wanting keyless, pay-per-use API access settled in USDC on Base
- —AI agents that can handle x402 payment challenges natively
- —Quick one-off data retrieval without subscription commitments
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —High-volume batch processing where per-request pricing may add up
- —Users without access to USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/237/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI schema, no request/response examples, and all documentation pages behind wallet-connect walls yielded no content. The specific purpose of this receipt endpoint is unclear beyond its URL path.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —All doc pages (/docs, /pricing, /README) require wallet connection and returned no useful content
- —The specific data returned by the transaction receipt endpoint is unknown — no response examples exist
- —This appears to be a single transaction-specific receipt (ID 237); generalizability is unclear
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/237/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/237/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com