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 198) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/198/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The 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 timeout of 300 seconds.
The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all returned only a "Connect wallet" prompt with no substantive content, so the actual response schema and detailed behavior of this endpoint are unknown. The broader site lists many other endpoints (sentiment analysis, summarization, embeddings, price feeds, geocoding, etc.) at the same $0.02 price point, but none have documented request/response schemas in the crawled material.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 198 via a micropayment-gated API
- —Demonstrating x402 protocol integration for pay-per-call services
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to fetch transaction receipts with crypto micropayments
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Users needing detailed API documentation or response schema guarantees
- —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/198/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (returns a valid x402 402 challenge), and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documented request/response format, and all documentation pages are empty stubs showing only 'Connect wallet'. The specific purpose of this receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —All documentation pages (/docs, /pricing, /api, /README) returned no useful content — only 'Connect wallet' prompts.
- —No request or response schema is available; the actual data returned by this endpoint is unknown.
- —The endpoint path references a specific transaction ID (198), which may indicate a demo or placeholder rather than a general-purpose API.
- —The platform lists many endpoints across diverse categories (AI, finance, geocoding, etc.) all at $0.02 — it is unclear whether these are fully functional or placeholders.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/198/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/198/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Platform lists endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com