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 246) 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/246/receipt) is live and 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 translates to $0.02 per call, consistent with the site's advertised pricing. Payment is made via the "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are required; access is granted purely through x402 payment headers.
Documentation is extremely sparse — 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 platform appears to be a demonstration or early-stage deployment of x402-gated microservices.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction ID 246 via a single paid API call
- —Demonstrating x402 protocol integration for agent-purchasable endpoints
- —Testing micropayment flows on the Base network using USDC
Fit
Best for
- —Developers experimenting with x402 payment protocol integration
- —Agents needing pay-per-call access without API key management
- —Projects requiring USDC-settled micropayment API access on Base
Not for
- —Production workloads requiring documented schemas and SLAs
- —Bulk data retrieval where per-call pricing is cost-inefficient
- —Users without USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/246/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid USDC payment to receive the receipt.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 beyond a landing page listing, no request/response schema, and no examples of the actual payload. The specific endpoint (transaction 246 receipt) is narrow and unexplained. Effectively a stub listing.
Warnings
- —No OpenAPI spec or schema documentation available
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The endpoint is for a specific transaction ID (246) — unclear if this is parameterized or a fixed resource
- —No response schema or example output is documented anywhere
- —Platform may be a demo or early-stage deployment
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/246/receipt
- —Platform offers APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com