Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 236) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network with no API keys, no rate limits, and no commitments.
The specific endpoint probed — /api/v1/transactions/236/receipt — returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 "exact" scheme to the specified payTo address. The endpoint accepts POST requests and returns application/json. Documentation beyond the landing page is extremely thin: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail, schemas, or example payloads.
Because the endpoint path suggests a specific transaction receipt rather than a general-purpose API, its utility to arbitrary callers is unclear. The broader platform's advertised capabilities (AI, finance, analytics, utilities) are not documented with request/response schemas, so it is difficult to evaluate what data is actually returned. Treat this listing as a stub until richer documentation becomes available.
Capabilities
Use cases
- —Retrieving a transaction receipt for resource 236 via a single micropayment
- —Demonstrating x402 payment flow on the Base network
- —Programmatic access to paid data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base
- —Use cases needing keyless, pay-per-call API access
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based access without crypto wallets
- —Bulk data retrieval where per-call micropayments are impractical
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/236/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming pricing and payment details. However, there is no OpenAPI schema, no request/response examples, and all documentation pages beyond the landing page are empty ('Connect wallet' only). The specific endpoint path (/transactions/236/receipt) suggests a narrow resource rather than a general-purpose API, and its actual output is unknown.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) contain no usable content beyond 'Connect wallet'
- —No request or response schema available — actual payload structure is unknown
- —Endpoint path references a specific resource ID (236); unclear if this is a general-purpose endpoint or a single fixed resource
- —The broader platform advertises many API categories (AI, finance, analytics) but none are documented with schemas or examples
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge returned maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/transactions/236/receipt
- —Platform advertises APIs for analytics, AI/ML, finance/Web3, and infrastructure utilitieshttps://lowpaymentfee.com