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 113) 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/113/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 max amount of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout. No API keys or rate limits are advertised; access is purely gated by micropayment.
The platform's landing page lists 16 endpoints across four categories (Data & Analytics, AI & Machine Learning, Finance & Web3, Infrastructure), all at the same $0.02 price point. Documentation pages beyond the landing page returned only a "Connect wallet" prompt with no further technical detail, so the actual request/response schemas for this receipt endpoint are unknown. The endpoint is live and returning a proper 402 challenge.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 113 via 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 micropayment protocol
- —Agents that need on-demand receipt retrieval without subscription overhead
- —Applications requiring keyless, pay-as-you-go API access on Base
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or OpenAPI schemas before integrating
- —Applications requiring non-USDC or non-Base payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/113/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, confirming it works. However, there is no OpenAPI schema, no documentation beyond a landing page, no request/response examples, and the specific purpose of this 'transaction receipt' endpoint is unclear. The docs, pricing, and README pages all returned only 'Connect wallet' with no content.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —All documentation pages beyond the landing page return only 'Connect wallet' — no technical details
- —The purpose and response format of the /transactions/113/receipt endpoint are not documented
- —The broader platform lists 16 endpoints but none have documented request/response schemas
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/113/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/113/receipt
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —16 endpoints listed across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com