x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 206) behind an x402 paywall. It is part of a broader platform that offers multiple pay-per-request API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per call settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/206/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the accepted payment scheme (exact), the USDC asset contract on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`), and the maximum amount required of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). No API keys or rate limits are advertised; access is granted immediately upon valid payment.
Documentation on the site is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI schema, no request/response examples, and no description of what the receipt payload actually contains. The platform's landing page lists many endpoints across several categories, but the specific functionality of this transaction receipt endpoint is not documented beyond its title.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 206 via programmatic payment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agent-driven purchase of transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to fetch transaction receipts with instant crypto payment
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Production workloads requiring well-documented request/response schemas
- —Bulk retrieval of many different transaction receipts (only transaction 206 is exposed at this URL)
- —Users who need fiat payment options or cannot transact on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/206/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no documentation, no OpenAPI schema, no request/response examples, and the docs pages are empty stubs. The specific purpose and payload of the transaction receipt are undocumented, making this effectively a stub listing.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
- —No OpenAPI or schema describing request parameters or response format.
- —The endpoint is for a single hardcoded transaction ID (206); unclear if other transaction IDs are available at similar paths.
- —No information on what the receipt payload contains or what inputs the POST body expects.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, scheme 'exact', network 'base', maxAmountRequired 20000, and USDC asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/transactions/206/receipt
- —The platform advertises $0.02 per request, no API keys, no rate limits, instant access, on Base network.https://lowpaymentfee.com
- —The platform lists endpoints across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categories.https://lowpaymentfee.com
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no additional content.https://lowpaymentfee.com/docs