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 238) 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/238/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 — consistent with the site's advertised pricing. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using the "exact" payment scheme. No API keys or rate limits are advertised; access is granted purely through on-chain payment.
Documentation is extremely thin — 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 endpoint is live (402 challenge confirmed), 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 238 via a single micropayment
- —Programmatic access to paid API endpoints without API key management
- —Agent-driven data retrieval with on-chain USDC settlement
Fit
Best for
- —Developers wanting keyless, pay-per-use API access on Base
- —AI agents that can settle x402 payments in USDC
- —Users who need transaction receipt data without subscription commitments
Not for
- —Users needing detailed API documentation or response schema before purchasing
- —High-volume batch retrieval where per-call pricing may add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/238/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment to access.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 documentation of request parameters or response schema, and the docs/pricing/README pages are all empty beyond a wallet connect prompt. The specific purpose of this particular receipt endpoint is unclear.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
- —No OpenAPI or JSON schema describing request body or response format
- —The endpoint is for a specific transaction ID (238); unclear if this is a demo or a real resource
- —The broader platform advertises many API categories (AI, finance, analytics, etc.) but none have documented schemas
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, on Base networkhttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/transactions/238/receipt
- —Platform offers APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com