x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 205) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network, with no API keys, no rate limits, and no minimum commitments.
This specific endpoint (/api/v1/transactions/205/receipt) returned a live x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the site's advertised pricing. The payment scheme is "exact" and the payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. The response MIME type is application/json.
Documentation on the site is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The endpoint is confirmed live via the 402 challenge, but the lack of documentation makes it difficult to know what data is returned or what input (if any) the POST body expects.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 205 via a single micropayment
- —Programmatic access to paid API resources without API key management
- —Agent-driven workflows that settle per-call costs in USDC on Base
Fit
Best for
- —Developers or agents needing keyless, pay-per-use API access on Base
- —Workflows requiring on-chain micropayment settlement in USDC
- —Quick one-off data retrieval without subscription commitments
Not for
- —High-volume batch processing where per-call fees add up quickly
- —Users who need detailed API documentation or schema guarantees before integrating
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/205/receipt
# Returns 402 with x402 challenge. Include X-PAYMENT header with valid payment proof to receive the receipt.Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a landing page listing, no request/response schema, and no examples. The specific purpose of this particular receipt endpoint (transaction 205) is unexplained. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — /docs, /api, /pricing, /README all return only a wallet-connect prompt
- —The specific resource (transaction 205 receipt) is unexplained; unclear what data the receipt contains
- —No request body schema documented for the POST method
- —The broader platform lists many endpoints but none have documented schemas or examples
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge returned with maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/transactions/205/receipt
- —Platform offers APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com