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 retrieval service. The specific resource `/api/v1/transactions/154/receipt` returns a receipt for transaction 154 in JSON format, payable per-call with USDC on the Base network. The x402 challenge confirms the endpoint is live, accepting POST requests with an exact payment scheme.
The broader lowpaymentfee.com platform advertises a suite of pay-per-request 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, settled in USDC on Base. The platform advertises no API keys, no rate limits, and instant access.
However, documentation is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation for any endpoint. The specific transaction receipt endpoint probed here has a maxAmountRequired of 20000 base units of USDC (6 decimals), which equals $0.02. The payTo address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` and the asset contract is the canonical Base USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`).
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Agent-driven access to financial data without pre-registration or API keys
- —Integrating pay-as-you-go receipt lookups into automated workflows
Fit
Best for
- —Agents needing keyless, pay-per-call access to transaction data
- —Developers experimenting with x402 payment protocol on Base
- —Use cases requiring no subscription or rate-limit constraints
Not for
- —Production workloads requiring detailed API documentation and SLAs
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/154/receipt \
-H "X-PAYMENT: <x402_payment_header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs showing only 'Connect wallet'. The specific purpose of the transaction receipt endpoint is only inferable from the URL path. Effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all render only 'Connect wallet'
- —No OpenAPI or JSON schema describing request parameters or response format
- —No example responses available; actual output format is unknown
- —The endpoint path references a specific transaction ID (154); it is unclear whether other transaction IDs are supported or how they are discovered
- —Platform advertises many endpoints but none have verifiable documentation
Citations
- —Endpoint returns 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/transactions/154/receipt
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/154/receipt
- —Asset contract is Base USDC at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/154/receipt
- —Platform lists $0.02/request pricing with no API keys, no rate limitshttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages show only 'Connect wallet'https://lowpaymentfee.com/docs