x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 117) behind an x402 paywall. The site advertises itself as a platform hosting multiple pay-per-call API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/117/receipt` returns a JSON response upon payment. The x402 challenge confirms the endpoint is live, accepting POST requests with an exact-payment scheme. The maximum amount required is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the receipt payload actually contains. The site's landing page lists many endpoints across different domains (sentiment analysis, summarization, geocoding, etc.), but without documentation it is unclear how functional or complete these services are. The lack of any detailed documentation or output schema beyond the x402 challenge significantly limits confidence in what this endpoint delivers.
Capabilities
Use cases
- —Retrieving a transaction receipt for resource ID 117 via programmatic x402 payment
- —Demonstrating x402 protocol integration with USDC on Base
- —Agent-driven pay-per-call access to gated API resources
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access without API keys
- —Low-cost micropayment API consumption on Base
Not for
- —Production workloads requiring documented response schemas and SLAs
- —Users who need detailed API documentation before integrating
- —Bulk data retrieval where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/117/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment on Base to receive the receipt.Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation, no OpenAPI schema, no request/response examples, and no description of what the receipt payload contains. Docs pages return only 'Connect wallet' with no content.
Warnings
- —No API documentation available — all doc pages render only 'Connect wallet'
- —No OpenAPI or output schema describing the response payload
- —Unknown what 'transaction 117 receipt' actually contains
- —No request body schema documented for the POST method
- —Multiple advertised endpoints (AI, finance, utils) have no verifiable documentation
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/117/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/117/receipt