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 126) behind an x402 paywall. It is part of a broader platform that advertises multiple 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/126/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers receive a 402 challenge containing payment parameters (asset: USDC on Base, maxAmountRequired: 20000 base units = $0.02, payTo address, 300-second timeout). Once the caller provides a valid X-PAYMENT header, the endpoint returns the receipt data. No API keys or rate limits are advertised; access is purely pay-per-call.
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 platform lists many other endpoints across analytics, AI, finance, and utility categories, but the specific functionality of this transaction receipt endpoint is not documented beyond its title.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 126 via a single paid API call
- —Demonstrating x402 protocol integration for pay-per-request workflows
- —Agent-driven programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing keyless, pay-per-call access to receipt data
- —Testing micropayment-gated API patterns
Not for
- —Bulk retrieval of many different transaction receipts (only transaction 126 is exposed at this URL)
- —Users who need detailed API documentation or response schema before integrating
- —Production workflows requiring SLA guarantees or documented error handling
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/126/receipt
# Returns 402 with x402 challenge. Supply X-PAYMENT header with valid USDC payment on Base to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming it is operational. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no response schema, no examples, and the specific purpose of a receipt for 'transaction 126' is unclear. The listing is effectively a stub with confirmed liveness.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) contain no substantive content — only a 'Connect wallet' prompt.
- —No OpenAPI or response schema available; the actual payload structure of the receipt is unknown.
- —This endpoint is scoped to a single transaction ID (126); it is unclear whether other transaction IDs are available at similar paths.
- —The broader platform advertises many endpoints (AI, analytics, finance, utilities) but none have documented schemas or examples.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/126/receipt
- —The platform advertises $0.02 per request across all API categories with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages render only a 'Connect wallet' prompt with no substantive contenthttps://lowpaymentfee.com/docs
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/126/receipt