Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 336) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of APIs spanning data & analytics, AI/ML inference (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, payable in USDC on the Base network with no API keys, no rate limits, and no commitments required.
The specific probed endpoint (`/api/v1/transactions/336/receipt`) returned a live 402 challenge using the x402 "exact" scheme. It accepts USDC (contract 0x8335…2913) on Base, with a maxAmountRequired of 20000 base units — which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. 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 technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The exact content returned by the receipt endpoint after payment is unknown. The platform appears to be a demonstration or early-stage x402 API marketplace.
Capabilities
Use cases
- —Retrieving a transaction receipt after paying $0.02 in USDC on Base
- —Demonstrating x402 protocol payment flows for agent-to-agent commerce
- —Accessing pay-per-call APIs without API key registration
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call API access on Base
- —Projects exploring micropayment-gated API patterns
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based API access
- —Applications requiring high-throughput with guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/336/receipt \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($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 the /transactions/336/receipt resource is unclear. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — all /docs, /api, /pricing, /README pages return only 'Connect wallet'
- —The exact request body format and response payload for this endpoint are unknown
- —The platform appears to be early-stage or a demo; no SLA or support information found
- —The specific meaning of 'transaction 336 receipt' is undocumented
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base with 300-second timeouthttps://lowpaymentfee.com/api/v1/transactions/336/receipt