Pay-per-call transaction receipt endpoint on Base via x402, priced at $0.02 in USDC.
What it does
This endpoint at lowpaymentfee.com provides a "Premium API Access" receipt resource for transaction ID 300. It is part of a broader platform offering dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated via the x402 payment protocol on the Base network.
The specific endpoint `/api/v1/transactions/300/receipt` accepts POST requests and returns JSON. Payment is settled in USDC (contract 0x8335…2913 on Base) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). There are no API keys, no rate limits, and no subscription commitments — each call is paid individually via the X-PAYMENT header. The payment timeout is 300 seconds.
Documentation on the site 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 schema, no request/response examples, and no detailed description of what the receipt endpoint actually returns. The broader platform advertises categories like sentiment analysis, text summarization, embeddings, geocoding, price feeds, and more — all at $0.02 per request — but without documentation it is unclear what data or functionality each endpoint actually provides.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 300 via a single paid API call
- —Demonstrating x402 payment-gated API access on Base
- —Integrating pay-per-request endpoints into agent workflows without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call API access on Base
- —Low-volume consumers who prefer no subscription commitments
Not for
- —Users needing detailed API documentation or guaranteed SLAs
- —High-volume batch processing where per-request pricing is inefficient
- —Anyone requiring non-USDC or non-Base payment settlement
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/300/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and all documentation pages render only 'Connect wallet' with no usable content. The purpose of this specific receipt endpoint is not explained beyond its generic title. Effectively a stub listing.
Warnings
- —No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or output schema describing request parameters or response format
- —The specific purpose and data returned by /api/v1/transactions/300/receipt is undocumented
- —The endpoint path contains a hardcoded transaction ID (300), suggesting it may be a demo or single-resource endpoint
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/300/receipt
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/300/receipt
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no documentation contenthttps://lowpaymentfee.com/docs