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 "Premium API Access" receipt for transaction ID 120 via a POST request. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning 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.
Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) through the x402 "exact" scheme. The maximum amount required per call is 20,000 base units, which at 6 decimals equals $0.02 USD. The endpoint returns application/json and has a payment timeout of 300 seconds. No OpenAPI schema or detailed documentation was found beyond the landing page listing.
The specific endpoint probed (/api/v1/transactions/120/receipt) appears to be a transaction receipt retrieval service. The broader platform advertises endpoints for sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, validation, conversion, and more — all at the same $0.02 price point. However, no detailed request/response schemas or documentation pages were accessible during the crawl (docs, API, pricing, and README pages all returned only a "Connect wallet" prompt).
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payments
- —Agents autonomously purchasing API access without pre-registration or API keys
- —Integrating pay-as-you-go data endpoints into workflows settled on Base L2
Fit
Best for
- —AI agents needing keyless, pay-per-call API access
- —Developers wanting low-friction micropayment APIs on Base
- —Use cases requiring transaction receipt data without subscription commitments
Not for
- —High-volume batch processing where per-call pricing becomes expensive
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Applications requiring non-crypto payment settlement
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/120/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, and all documentation pages returned only a wallet-connect prompt. The specific purpose of this particular endpoint (transaction 120 receipt) is vague, and the broader platform's actual functionality behind each listed endpoint is unverifiable.
Warnings
- —No OpenAPI or detailed API documentation available — all doc pages return only 'Connect wallet'
- —The endpoint path references a hardcoded transaction ID (120), making its general-purpose utility unclear
- —No request body schema or response schema documented anywhere
- —Platform lists many endpoints but none could be verified for actual functionality beyond the 402 challenge
Citations
- —Endpoint returns 402 with x402 challenge requiring 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/120/receipt
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/120/receipt
- —Platform offers endpoints across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com