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 71) 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/71/receipt` accepts POST requests and returns an `application/json` response. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header containing a signed payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to the merchant address `0x1A2B…85F3`. The payment scheme is "exact" with a 300-second timeout window. 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. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) returned only a "Connect wallet" prompt with no substantive content, so the actual behavior and response schema of this specific receipt endpoint — and the other listed endpoints — cannot be verified from available materials.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 71 via micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agent-driven on-demand data retrieval without pre-registration or API keys
Fit
Best for
- —Developers experimenting with x402 micropayment protocol
- —Agents that need keyless, pay-as-you-go API access on Base
- —Projects requiring USDC-settled per-call billing without subscriptions
Not for
- —Users needing free or subscription-based API access
- —Production workloads requiring documented response schemas and SLAs
- —Bulk data retrieval where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/71/receipt \
-H "X-PAYMENT: <x402-signed-payment>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no response schema, no example payloads, and the docs/pricing/README pages are all empty stubs showing only 'Connect wallet'. The purpose of this specific receipt endpoint is unclear beyond its URL path.
Warnings
- —Documentation pages (/docs, /pricing, /api, /README) contain no useful content — only a 'Connect wallet' prompt.
- —No response schema or example response is available for this endpoint.
- —The specific purpose and data returned by /api/v1/transactions/71/receipt is undocumented and cannot be verified.
- —The broader platform lists 16 endpoints but none have documented request/response formats.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/71/receipt
- —The platform lists 16 endpoints across four categories all priced at $0.02 per requesthttps://lowpaymentfee.com
- —Pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages return only a 'Connect wallet' prompt with no substantive contenthttps://lowpaymentfee.com/docs