Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 245) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme. The price per call is $0.02 (20,000 base units with 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments required.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The specific endpoint probed (/api/v1/transactions/245/receipt) is not listed on the homepage's API catalog, so its exact purpose and response format are unclear. The x402 challenge confirms the endpoint is live and accepting payment negotiations.
Capabilities
Use cases
- —Retrieving transaction receipt data via a single micropayment
- —Agent-driven pay-per-call access without API key management
- —Programmatic access to receipt records settled on Base L2
Fit
Best for
- —Agents or scripts that need keyless, pay-per-use API access
- —Developers experimenting with x402 payment protocol integrations
- —Use cases requiring on-chain USDC micropayments on Base
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —High-volume batch processing 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/245/receipt
# Returns 402 with x402 payment challenge.
# Include X-PAYMENT header with a valid x402 payment proof to receive the receipt.Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation for request/response schemas, no OpenAPI spec, and the specific endpoint is not listed in the site's own catalog. The docs pages are empty beyond a wallet connect prompt, making integration highly uncertain.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —The probed endpoint (/api/v1/transactions/245/receipt) is not listed on the provider's homepage API catalog
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The platform lists many API categories but provides no evidence of actual functionality behind them
Citations
- —The x402 challenge returns maxAmountRequired of 20000 in USDC (6 decimals) on Base network, equating to $0.02https://lowpaymentfee.com/api/v1/transactions/245/receipt
- —The homepage lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categories all at $0.02/requesthttps://lowpaymentfee.com
- —Pricing is $0.02/request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages render only a 'Connect wallet' prompt with no technical contenthttps://lowpaymentfee.com/docs