Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 390) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, the specific endpoint being listed here is the transaction receipt resource at `/api/v1/transactions/390/receipt`.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what the receipt payload actually contains. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the lack of documentation makes it difficult to assess the actual utility or data returned.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 390 via a micropayment
- —Demonstrating x402 pay-per-call integration on Base
- —Agent-driven data retrieval with per-request USDC settlement
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need to fetch transaction receipts without API keys
- —Low-cost per-call data access on Base network
Not for
- —Production use requiring documented request/response schemas
- —Bulk or high-volume receipt retrieval (no batch endpoint documented)
- —Users without USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/390/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment proof on Base to receive the receipt.Endpoint
Quality
The endpoint is confirmed live via a valid 402 x402 challenge, 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 technical content. The specific resource (transaction 390 receipt) is narrow and unexplained.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet'
- —No OpenAPI or schema describing request parameters or response format
- —The endpoint is scoped to a single transaction ID (390); unclear if this is a demo or production resource
- —No information on what the receipt payload contains
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/390/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 lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/390/receipt