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 53) 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 and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/53/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 maxAmountRequired of 20,000 base units of USDC (0x8335…2913 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 markets itself as requiring no API keys, no rate limits, and no commitments — just per-request micropayments. However, documentation is extremely sparse: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The exact data returned by this receipt endpoint is unknown beyond the stated mimeType of application/json.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 53 via micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Programmatic access to financial transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that can settle USDC micropayments on Base
- —Use cases needing keyless, per-request API access
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —High-volume batch retrieval where per-request pricing is inefficient
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/53/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page listing, and no examples. The specific purpose of this receipt endpoint is vague. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The endpoint is for a specific transaction ID (53); it is unclear whether this is a demo or a production resource
- —No examples of request body or response payload could be found
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/53/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/53/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Available API categories include Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com