x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 108) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (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 via the x402 protocol.
The specific endpoint probed (/api/v1/transactions/108/receipt) returns a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the site's advertised pricing. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. No API keys or rate limits are required; access is instant upon payment.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The endpoint is live and responding with a proper 402 challenge, but the lack of documentation makes it difficult to know what data is returned or what input parameters (if any) the POST body expects.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction 108 via a single paid API call
- —Programmatic access to paid API endpoints without managing API keys or subscriptions
- —Agent-driven workflows that need to pay-per-request for data retrieval on Base
Fit
Best for
- —Developers wanting keyless, pay-per-use API access settled in USDC on Base
- —AI agents that can autonomously pay for API calls via x402
- —Quick one-off data retrieval without subscription commitments
Not for
- —Users needing detailed API documentation or response schema guarantees before integrating
- —High-volume use cases where per-request pricing may be less economical than a subscription
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/108/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it works. However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty stubs. The specific purpose of this receipt endpoint is unclear beyond its URL path. Pricing is clear ($0.02/request in USDC on Base).
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) are all empty — only show 'Connect wallet' with no technical content
- —No OpenAPI or schema documentation available for any endpoint
- —No response schema or example payloads documented — unknown what data the receipt endpoint actually returns
- —The specific endpoint is for transaction ID 108; it is unclear whether this is a demo resource or a production receipt
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, which equals $0.02https://lowpaymentfee.com/api/v1/transactions/108/receipt
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com