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 127) 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 services — all priced at $0.02 per call, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/127/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… 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, /README) appear to require a wallet connection and contain no substantive content in the crawl. There is no OpenAPI spec, no detailed schema for request or response bodies, and no examples of what the receipt payload actually contains. The broader site lists many other endpoints (analytics, AI, finance, utilities) at the same $0.02 price point, but this specific listing covers only the transaction receipt resource.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction via programmatic payment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agents that need to fetch financial transaction records without API key registration
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing keyless, pay-per-call access to transaction data
- —Low-friction API access without subscription or signup
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Production systems requiring SLA guarantees or documented error handling
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/127/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI spec, no request/response schema, no documentation content (all doc pages just show 'Connect wallet'), and the endpoint path is hardcoded to a single transaction ID (127), making its general utility unclear. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All documentation pages (/docs, /pricing, /README) returned only 'Connect wallet' with no substantive content
- —Endpoint path is hardcoded to transaction ID 127; unclear if other transaction IDs are supported or how to discover them
- —No examples of actual response payload available
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/127/receipt
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/127/receipt
- —Platform pricing is $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