Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/142/receipt`. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The endpoint responds to POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers include an `X-PAYMENT` header with a signed payment of up to 20,000 base units of USDC (i.e., $0.02, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. No API keys, rate limits, or upfront commitments are required — access is instant upon valid payment.
The specific endpoint probed (`/api/v1/transactions/142/receipt`) appears to serve a receipt for transaction ID 142. The broader platform advertises categories including metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation endpoints. Documentation pages exist but returned only a "Connect wallet" prompt with no substantive content, so detailed request/response schemas are unavailable.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC micropayments
- —Agents autonomously purchasing API access without pre-registration or API keys
- —Integrating pay-as-you-go data endpoints into Web3 workflows
Fit
Best for
- —AI agents needing keyless, instant API access with crypto micropayments
- —Developers wanting pay-per-call pricing without subscriptions
- —Web3 applications that settle on Base network in USDC
Not for
- —Users who need free or ad-supported API access
- —Applications requiring detailed OpenAPI documentation and typed schemas before integration
- —High-volume batch processing where per-call pricing becomes expensive
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/142/receipt \
-H "X-PAYMENT: <x402-signed-payment>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, documentation pages are empty (only 'Connect wallet'), there is no OpenAPI spec, no request/response schema, and no examples. The specific purpose of this particular receipt endpoint (transaction 142) is unclear — it may be a demo or placeholder. Effectively a stub listing.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) all returned only 'Connect wallet' with no substantive content
- —No OpenAPI or request/response schema available — request body format and response structure are unknown
- —The endpoint path references a specific transaction ID (142), which may be a demo/placeholder rather than a general-purpose resource
- —The broader platform advertises many endpoints but none have documented schemas
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/142/receipt
- —Platform advertises $0.02 per request pricing across all endpointshttps://lowpaymentfee.com
- —No API keys, no rate limits, instant access advertisedhttps://lowpaymentfee.com
- —USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/142/receipt
- —maxAmountRequired is 20000 base units = $0.02 (USDC has 6 decimals)https://lowpaymentfee.com/api/v1/transactions/142/receipt