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 endpoint `/api/v1/transactions/78/receipt` returns a receipt for transaction ID 78 in JSON format, gated behind a per-call USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live and accepts exact-scheme payments of up to 20,000 base units of USDC (0.02 USD) per request.
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 commitments required. Payments settle in USDC on the Base L2 network.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available from the crawl. The exact behavior and response format of this receipt endpoint must be inferred from the endpoint path and the x402 challenge metadata alone.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically via micropayment
- —Integrating pay-per-call receipt lookups into agent workflows
- —Accessing financial transaction data without API key registration
Fit
Best for
- —Agents needing on-demand transaction receipt data with no signup
- —Developers experimenting with x402 micropayment-gated APIs
- —Workflows requiring low-cost, keyless API access on Base
Not for
- —Bulk retrieval of many transaction receipts (no documented batch endpoint)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Applications requiring non-USDC or non-Base payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/78/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing and payment details, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. No OpenAPI spec, no request/response schemas, and no usage examples are available. The endpoint's actual response format is unknown.
Warnings
- —Documentation pages (/docs, /pricing, /api, /README) all return only a 'Connect wallet' prompt with no technical content
- —No OpenAPI or schema documentation available for any endpoint
- —The specific endpoint path references a hardcoded transaction ID (78); it is unclear whether this is a demo or a real parameterized resource
- —Response format and fields are completely undocumented
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (0.02 USD) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/78/receipt
- —All endpoints are listed at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform advertises APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs