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 a transaction receipt for transaction ID 233 via a POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced uniformly at $0.02 per request with no API keys, no rate limits, and no commitments required.
The specific endpoint `/api/v1/transactions/233/receipt` returns a JSON response and is gated by an x402 payment challenge. Payment is settled on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The payment timeout is 300 seconds. The endpoint was confirmed live, returning a proper 402 challenge with x402 version 1.
The platform's documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all appear to be behind a wallet-connect gate and contain no substantive content in the crawl. As a result, there is no detailed API documentation, request/response schema, or usage examples available beyond what the x402 challenge and the landing page provide. The exact nature of the "receipt" data returned after payment is not documented in the crawled material.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 233 via a single paid API call
- —Demonstrating x402 payment protocol integration for agent-to-service commerce
- —Programmatic access to receipt data without traditional API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing keyless, pay-per-call API access settled in USDC
- —Low-friction one-off data retrieval without subscription commitments
Not for
- —Bulk or high-volume receipt retrieval (no documented batch endpoints)
- —Users who need detailed API documentation or response schema before purchasing
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/233/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no API documentation, no request/response schema, no examples, and the docs pages are all behind a wallet-connect wall with no content. The specific purpose of this particular receipt endpoint (transaction 233) is unclear.
Warnings
- —All documentation pages (/docs, /pricing, /api, /README) returned only a 'Connect wallet' prompt with no usable content.
- —No request body schema or response schema is documented — the output of this endpoint after payment is unknown.
- —The endpoint is hardcoded to transaction ID 233; it is unclear whether this is a demo or a real transaction receipt.
- —The broader platform lists many API categories (AI, analytics, finance, utilities) but none were probed; only this single receipt endpoint is confirmed live.
Citations
- —Endpoint returns 402 with x402 version 1 challenge, accepting USDC on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/transactions/233/receipt
- —Platform advertises $0.02 per request pricing 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/233/receipt
- —Platform offers APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com