Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt retrieval service accessible via the x402 payment protocol. The specific resource `/api/v1/transactions/342/receipt` returns a JSON receipt when called with a valid X-PAYMENT header containing a USDC payment on the Base network.
The endpoint is part of a broader platform (lowpaymentfee.com) that offers multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced uniformly at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access; payment is handled entirely through the x402 protocol using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on the Base L2 network.
The x402 challenge confirms the endpoint is live, accepting POST requests with an exact payment scheme. The maxAmountRequired is 20000 base units of USDC (6 decimals), which equals $0.02. The payment timeout is 300 seconds. No OpenAPI schema, detailed documentation, or example responses are available beyond the landing page listing.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Integrating pay-per-use APIs without managing API keys or subscriptions
- —Demonstrating x402 protocol payment flows on Base network
Fit
Best for
- —Agents or services needing on-demand transaction receipts without subscription overhead
- —Developers experimenting with x402 protocol integrations
- —Applications that prefer crypto-native per-call billing on Base
Not for
- —High-volume batch receipt retrieval where per-call pricing is inefficient
- —Users without USDC on Base network
- —Applications requiring detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/342/receipt \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via 402 challenge and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no example request/response bodies, and documentation pages all just show 'Connect wallet' with no actual content. The specific purpose of this particular receipt endpoint (transaction 342) is unclear.
Warnings
- —No API documentation available — all doc pages render only 'Connect wallet'
- —No OpenAPI or schema describing request/response formats
- —The endpoint path references a specific transaction ID (342), which may indicate a demo or placeholder rather than a general-purpose endpoint
- —No information on what data the receipt contains or what inputs are expected in the POST body
Citations
- —Endpoint returns 402 with x402 challenge requiring 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/342/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/342/receipt