x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 16) 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 and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/16/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers receive a 402 challenge specifying the USDC asset contract on Base (`0x8335…`), and must attach an `X-PAYMENT` header with a signed payment of up to 20,000 base units (i.e., $0.02 USDC, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a 300-second timeout.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The platform's landing page lists many endpoints across several domains but provides no detail on inputs, outputs, or data sources. Treat this listing as a stub until richer documentation becomes available.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction via programmatic API call
- —Demonstrating x402 payment-gated API access on Base
- —Integrating pay-per-call receipt retrieval into an agent workflow
Fit
Best for
- —Developers experimenting with x402 protocol payments on Base
- —Agents that need to fetch transaction receipts without API keys
- —Micropayment-based API consumption with no subscription commitment
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk or batch receipt retrieval (no documented batch endpoint)
- —Users who need fiat-only payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/16/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment on Base to access.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI spec, no request/response examples, and the docs pages are empty. The purpose of this specific receipt endpoint is unclear beyond its URL path. Effectively a stub.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown.
- —Docs, pricing, API, and README pages all render only 'Connect wallet' with no usable content.
- —The specific resource '/api/v1/transactions/16/receipt' is a single hard-coded transaction ID; unclear if other IDs are available or what the receipt contains.
- —The platform lists many endpoints on its landing page but none have documented inputs or outputs.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02).https://lowpaymentfee.com/api/v1/transactions/16/receipt
- —The platform lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categories, all at $0.02 per request.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/transactions/16/receipt