Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt retrieval service behind an x402 paywall. When called via POST, it returns a JSON receipt for transaction ID 271. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).
The parent site lowpaymentfee.com hosts a broader suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto market data, and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are advertised at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payment is handled entirely through the x402 protocol on the Base L2 network.
Documentation is extremely sparse — 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 usage examples available from the crawl. The specific endpoint probed (/api/v1/transactions/271/receipt) is live and returns a valid x402 challenge, but what the receipt payload actually contains is unknown beyond the stated mimeType of application/json.
Capabilities
Use cases
- —Retrieving a JSON receipt for a specific transaction via a single paid API call
- —Demonstrating x402 protocol integration for pay-per-call services on Base
- —Programmatic receipt fetching without API key registration
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand transaction receipts without subscription overhead
- —Projects that want keyless, pay-as-you-go API access on Base
Not for
- —Bulk receipt retrieval at scale (no documented batch endpoint)
- —Users who need detailed API documentation or response schema guarantees
- —Applications requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/271/receipt \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the purpose of this specific receipt endpoint (transaction 271) is unclear. The listing is effectively a stub.
Warnings
- —No API documentation available; /docs, /pricing, /api, and /README pages all render only 'Connect wallet'
- —No OpenAPI or output schema provided — response format is unknown beyond application/json
- —The endpoint is hardcoded to transaction ID 271; it is unclear whether other transaction IDs are supported or what the receipt contains
- —The broader site advertises many endpoints but none have documented schemas or examples
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/271/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The site offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/271/receipt