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 access to a transaction receipt resource (transaction ID 184) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme. The advertised cost is 20,000 base units of USDC, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at the same $0.02/request price point. However, this specific listing covers only the `/api/v1/transactions/184/receipt` endpoint.
Documentation is extremely sparse. The docs, API, pricing, and README pages all returned 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 endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know what data is returned or what request body (if any) is expected.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 184 via a single paid API call
- —Demonstrating x402 payment-gated API access on the Base network
- —Integrating pay-per-call receipt retrieval into agent workflows without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents needing on-demand transaction receipt data without subscription commitments
- —Projects requiring USDC-settled micropayment API access on Base
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto workflows that cannot produce x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/184/receipt \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs showing only 'Connect wallet'. The specific purpose of this receipt endpoint is unclear beyond its URL path.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) contain no substantive content — only a 'Connect wallet' prompt.
- —No OpenAPI or schema definition available; request body and response format are unknown.
- —This endpoint is for a specific transaction ID (184); it is unclear whether other transaction IDs are available or how they are discovered.
- —The broader platform lists many API categories (AI, finance, analytics, etc.) but none have documented schemas or examples.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/184/receipt
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/184/receipt
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) show only 'Connect wallet' with no contenthttps://lowpaymentfee.com/docs