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 162) 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 (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/162/receipt` — returns a valid x402 challenge (version 1, scheme "exact") requesting up to 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 with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
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 usage examples available from the crawl. The platform appears functional (root returns 200, x402 challenge is live), but without documentation it is difficult to know what request body to send or what the response payload looks like.
Capabilities
Use cases
- —Retrieving transaction receipt data for a specific transaction via micropayment
- —Programmatic access to paid API resources without API key management
- —Agent-driven workflows that need on-demand receipt retrieval settled in USDC
Fit
Best for
- —Developers wanting keyless, pay-per-use API access on Base
- —AI agents that can settle x402 payments autonomously
- —Users who need transaction receipt data without subscription commitments
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —High-volume batch processing where per-request pricing may add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/162/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, and all documentation pages render only a wallet-connect prompt. The specific purpose of this particular receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema describing request body or response format
- —The specific endpoint is for transaction ID 162; unclear if this is a demo or a real resource
- —No examples of successful responses available from crawl material
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge requests maxAmountRequired of 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02https://lowpaymentfee.com/api/v1/transactions/162/receipt
- —Platform offers APIs across data & analytics, AI/ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com