x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 289) behind an x402 paywall. The site advertises itself as a platform hosting multiple pay-per-request API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/289/receipt` returns a JSON response upon payment. The x402 challenge confirms the endpoint is live, accepting exact-scheme payments of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are required — access is purely payment-gated.
Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The broader site lists many endpoints across analytics, AI, finance, and utility categories, but none have documented schemas. Treat this as a functional but poorly documented endpoint.
Capabilities
Use cases
- —Retrieving a transaction receipt for record ID 289 via a single paid request
- —Demonstrating x402 payment-gated API access patterns
- —Programmatic receipt retrieval without API key management
Fit
Best for
- —Agents or developers experimenting with x402 payment protocols
- —Use cases requiring no-signup, pay-per-request API access on Base
- —Fetching transaction receipts with USDC micropayments
Not for
- —Production workflows requiring documented request/response schemas
- —Bulk or high-volume receipt retrieval (no documented batch support)
- —Users who need fiat payment rails or non-crypto settlement
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/289/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — docs/pricing/API pages all show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples of the actual receipt payload. The specific purpose of 'transaction 289 receipt' is unexplained.
Warnings
- —No documentation available — docs, pricing, API, and README pages all render only 'Connect wallet'
- —No OpenAPI or schema describing request parameters or response format
- —The specific meaning of 'transactions/289/receipt' is undocumented; unclear if the resource ID is parameterizable
- —The broader site lists many endpoints but none appear to have documented schemas
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/transactions/289/receipt
- —Price is $0.02 per request, settled in USDC on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/289/receipt
- —No API keys, no rate limits, instant access advertisedhttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages show only 'Connect wallet'https://lowpaymentfee.com/docs