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 43) 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/43/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 equals $0.02 per call. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. The endpoint accepts POST requests and returns application/json.
Documentation is extremely sparse — the /docs, /pricing, /api, 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 markets itself on simplicity (no API keys, no rate limits, instant access), but the lack of documentation makes it difficult to know what data any of these endpoints actually return.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction ID 43 via a single paid API call
- —Programmatic access to receipt information without API key registration
- —Agent-driven workflows that need to fetch financial transaction records on-demand
Fit
Best for
- —Developers wanting zero-signup, pay-per-use API access settled in USDC on Base
- —AI agents that can handle x402 payment challenges natively
- —Quick one-off transaction receipt lookups without subscription overhead
Not for
- —Users needing detailed API documentation or response schema guarantees before integrating
- —Bulk or high-volume receipt retrieval where per-call pricing adds up
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/43/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid payment proof to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming pricing and payment details. However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty. The specific endpoint appears to serve a single hardcoded transaction receipt (ID 43), which limits general utility. Effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content
- —No request or response schema is documented; it is unknown what fields the receipt contains
- —This endpoint targets a specific transaction ID (43); it is unclear whether other transaction IDs are available or how to discover them
- —The platform lists many other endpoints (AI, analytics, finance, utilities) but none have documented schemas or examples
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/43/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/43/receipt
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com