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 212) 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 infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/212/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. No API keys or rate limits are advertised; access is gated purely 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 response schema and request body format 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 212 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 with no subscription
- —Projects already operating on the Base L2 network with USDC
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or response schemas before integrating
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/212/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 documented request/response format, and the docs/pricing/README pages all returned only 'Connect wallet' with no usable content. The purpose of this specific receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No API documentation available — all doc pages return only 'Connect wallet'
- —Request body schema and response schema are completely unknown
- —The specific purpose and content of the transaction 212 receipt is undocumented
- —No OpenAPI or machine-readable schema provided
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/212/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/212/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform lists 16 endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com