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. When called via POST, it returns a JSON receipt for a specific transaction (in this case, transaction ID 234). Payment is handled inline using the x402 protocol: the endpoint returns a 402 challenge requiring a USDC payment on the Base network before serving the response.
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 at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. All payments settle on the Base L2 network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913).
The specific endpoint probed (/api/v1/transactions/234/receipt) costs up to $0.02 per call (maxAmountRequired of 20000 base units with USDC's 6 decimals = $0.02). The x402 challenge is live and well-formed, with a 300-second payment timeout. However, documentation beyond the landing page is essentially empty (all subpages just show "Connect wallet"), so the exact request body schema and response format are unknown. There is no OpenAPI spec or detailed docs available.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Integrating pay-per-use receipt lookups into agent workflows without API key management
- —Accessing financial transaction data via x402 protocol on Base L2
Fit
Best for
- —Agents or services that need on-demand transaction receipts without subscription commitments
- —Developers experimenting with x402 pay-per-call patterns on Base
- —Low-volume consumers who prefer micropayments over monthly API plans
Not for
- —High-volume batch receipt retrieval where per-call pricing becomes expensive
- —Users who need detailed API documentation or OpenAPI specs before integration
- —Applications requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/234/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment to proceed.Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payments. However, there is no OpenAPI spec, no documentation beyond a landing page, no request/response schema, and all doc/pricing/API subpages are empty ('Connect wallet' only). The specific endpoint path (/transactions/234/receipt) is not listed on the landing page, and the actual response payload is unknown.
Warnings
- —No OpenAPI spec or detailed documentation available — all doc pages return only 'Connect wallet'
- —The specific endpoint /api/v1/transactions/234/receipt is not listed among the advertised APIs on the landing page
- —Request body schema and response format are completely unknown
- —Platform appears to be a demo or early-stage project with placeholder documentation
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/234/receipt
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/234/receipt
- —Available API categories include Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com