x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 385) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (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 required.
The specific endpoint probed (/api/v1/transactions/385/receipt) returned 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 platform's advertised pricing. The payment scheme is "exact" and the payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. The endpoint accepts POST requests and returns application/json.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The platform appears functional but under-documented, making it difficult to know what data the receipt endpoint returns without paying for a call.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction ID 385 via a single paid API call
- —Programmatic access to receipt information without traditional API key registration
- —Agent-driven workflows that need to fetch financial transaction records on-demand
Fit
Best for
- —Agents or services that need on-demand transaction receipt retrieval with crypto-native payment
- —Developers exploring x402 protocol integrations on Base
- —Use cases where avoiding API key management is preferred
Not for
- —Bulk retrieval of many transaction receipts (each call costs $0.02 with no batch endpoint documented)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto-native applications that cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/385/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty. The specific purpose of this receipt endpoint is unclear beyond its URL path. This is effectively a stub listing.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
- —No request or response schema documented; unknown what fields the receipt contains
- —This endpoint is for a specific transaction ID (385); unclear if other transaction IDs are available or how to discover them
- —No OpenAPI or ai-plugin manifest found
Citations
- —Platform advertises $0.02 per request pricing 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/385/receipt
- —Platform lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs