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 (transaction ID 146) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/146/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 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The platform markets itself as requiring no API keys, no rate limits, and no commitments — just per-request micropayments. However, documentation beyond the landing page is essentially empty (all sub-pages only show a "Connect wallet" prompt), so the exact schema of request bodies and response payloads for this and other endpoints is undocumented. The endpoint is confirmed live via a valid 402 challenge response.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 146 via a single micropayment
- —Programmatic access to receipt data without traditional API key management
- —Agent-driven workflows that need on-chain-settled API calls
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need to fetch transaction receipts with no subscription overhead
- —Low-volume, on-demand receipt retrieval on Base network
Not for
- —High-volume batch receipt retrieval (no documented bulk endpoints)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/146/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema documentation, and all doc pages are empty stubs. The specific purpose of this receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No API documentation available — all doc/pricing/README pages return only a 'Connect wallet' prompt with no content.
- —Request and response schemas are completely undocumented; callers must guess at the POST body format.
- —The endpoint is for a specific transaction ID (146); it is unclear whether this is a demo or a production resource.
- —The broader platform lists many endpoints (AI, finance, analytics) but none have documented schemas.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/146/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/146/receipt
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and no commitmentshttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com