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 93) 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, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/93/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 max amount 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 advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /api) appear to require a wallet connection and contain no substantive content in the crawl. There is no OpenAPI spec, no detailed schema for request/response bodies, and no examples of what the receipt payload actually contains. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what data is returned.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 93 via a single micropayment
- —Programmatic access to paid API resources without API key management
- —Agent-driven workflows that need to fetch financial transaction data on-demand
Fit
Best for
- —Developers wanting keyless, pay-per-use API access settled in USDC on Base
- —AI agents that can handle x402 payment challenges natively
- —Users who prefer crypto micropayments over subscription billing
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —High-volume batch retrieval where per-request pricing is inefficient
- —Users without access to USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/93/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation content (all doc pages just show 'Connect wallet'), and no examples of what the receipt contains. The listing is essentially a stub with pricing and liveness confirmed.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no substantive content
- —The specific endpoint path references a hardcoded transaction ID (93); unclear if this is a demo or a real resource
- —No information on what fields the receipt response contains
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/93/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/93/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com