x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 159) 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, with no API keys, no rate limits, and no minimum commitments.
The specific endpoint probed — `/api/v1/transactions/159/receipt` — returned a valid x402 challenge (HTTP 402) requesting up to 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 the specified payTo address. 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 technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The nature of what the "Premium API Access" receipt endpoint actually returns is unclear — it may be a demo or placeholder resource rather than a production data service.
Capabilities
Use cases
- —Retrieving a transaction receipt via a single micropayment in USDC
- —Demonstrating x402 payment protocol integration on Base
- —Agent-driven pay-per-use API consumption without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access on Base
- —Testing USDC micropayment flows
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based API access
- —High-volume batch processing where per-call fees add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/159/receipt
# Returns HTTP 402 with x402 challenge.
# Attach X-PAYMENT header with a signed USDC payment ($0.02 on Base) to access the resource.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The purpose of this specific receipt endpoint is unclear, and all doc pages render only a wallet-connect prompt.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet'
- —No OpenAPI or request/response schema provided for any endpoint
- —The specific endpoint '/api/v1/transactions/159/receipt' labeled 'Premium API Access' has unclear purpose — may be a demo or placeholder
- —Cannot verify what data the endpoint actually returns without making a paid request
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Base (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)https://lowpaymentfee.com/api/v1/transactions/159/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform offers APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com