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 a transaction receipt resource at `/api/v1/transactions/321/receipt`. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments required.
The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base network, 6 decimals = $0.02) via the x402 "exact" scheme. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The response MIME type is application/json and the method is POST.
The platform's landing page lists 16 endpoints across four categories, but documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no detailed schema for request or response bodies, and no usage examples. The exact purpose of the "transaction receipt" resource (as opposed to the analytics, AI, or finance endpoints) is not documented. Treat this listing as a live but minimally documented x402 endpoint.
Capabilities
Use cases
- —Retrieving a transaction receipt via a single paid API call
- —Programmatic access to receipt data without API key management
- —Agent-driven workflows that need on-demand paid data retrieval
Fit
Best for
- —Developers wanting keyless, pay-per-use API access on Base
- —AI agents that can settle x402 payments in USDC
- —Quick one-off receipt lookups without subscription overhead
Not for
- —Users needing 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/321/receipt
# Returns 402 with x402 payment challenge.
# Attach X-PAYMENT header with a valid x402 payment proof to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page, and the specific purpose of the 'transactions/321/receipt' resource is undocumented. All doc pages returned only 'Connect wallet'.
Warnings
- —No OpenAPI or schema documentation available for request or response bodies
- —All documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no content
- —The specific function of the transaction receipt endpoint is not explained anywhere in the crawled material
- —The endpoint path contains a hardcoded ID (321), suggesting it may be a demo or example resource rather than a general-purpose API
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/321/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 16 endpoints across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimalshttps://lowpaymentfee.com/api/v1/transactions/321/receipt