x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (specifically for transaction ID 294) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/294/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The asset used is USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base) with a max amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The payment timeout is 300 seconds.
The platform advertises no API keys, no rate limits, and instant access. However, documentation beyond the landing page is essentially empty (all sub-pages just show "Connect wallet"), so there is no detailed schema, request/response format, or usage guidance available. The endpoint is live and returns a proper 402 challenge, but the actual functionality and response payload for this specific receipt endpoint remain undocumented.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 294 via a single micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Programmatic access to receipt data without API key registration
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base
- —Use cases requiring keyless, pay-per-call API access
Not for
- —Production workflows requiring documented request/response schemas
- —Bulk retrieval of multiple transaction receipts (only one transaction ID exposed)
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/294/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but documentation is effectively nonexistent — all doc/pricing/API pages render only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the endpoint appears to serve a single hardcoded transaction ID (294) with no explanation of what the receipt contains. This is essentially a stub listing.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) are all empty beyond 'Connect wallet'
- —No OpenAPI or schema available — request body and response format are unknown
- —Endpoint is scoped to a single transaction ID (294); unclear if other IDs are available
- —No information on what data the 'receipt' actually contains
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/294/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/294/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com