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 166) 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 utility/infrastructure services — all priced at $0.02 per call, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/166/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 x402 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 advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /api, /README) all appear to require a wallet connection and contain no substantive content in the crawl. As a result, the actual response schema, request body format, and detailed behavior of this specific receipt endpoint are unknown. The broader site lists many other endpoints (analytics, AI, finance, utilities) at the same $0.02 price point, but no OpenAPI spec or detailed documentation was found.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 166 via a micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand transaction receipt retrieval
- —Use cases requiring keyless, pay-per-call API access on Base
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/166/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation content beyond wallet-connect stubs, no request/response schema, and the specific purpose of this receipt endpoint is vague. The listing is effectively a stub with confirmed liveness and pricing.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown
- —All documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no usable content
- —The endpoint path references a specific transaction ID (166); it is unclear whether this is a generic pattern or a single fixed resource
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/166/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/166/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform offers endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com