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 a transaction receipt retrieval service. The specific resource `/api/v1/transactions/115/receipt` is one endpoint within a broader platform that offers data & analytics, AI & machine learning, finance & Web3, and infrastructure utility APIs — all priced at $0.02 per request and settled in USDC on the Base network.
The endpoint accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers supply an `X-PAYMENT` header containing a signed USDC payment on Base. The maximum amount required per call is 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals). There are no API keys, no rate limits, and no subscription commitments — each request is independently paid for at the time of the call.
The broader lowpaymentfee.com platform advertises additional endpoints across categories including sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, and more, all at the same $0.02 per-request price point. However, documentation beyond the landing page is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. The actual data returned by this specific receipt endpoint is not documented, so the response schema is unknown.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Integrating pay-per-use API access into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on the Base network
Fit
Best for
- —Agents or applications that need keyless, pay-per-call API access
- —Developers experimenting with x402 protocol integrations
- —Use cases requiring low-cost micropayment-settled API calls
Not for
- —Users who need detailed API documentation or response schema guarantees before integrating
- —High-volume batch processing where per-call payment overhead is impractical
- —Users without access to USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/115/receipt \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, documentation is nearly nonexistent — all doc/pricing/API pages show only 'Connect wallet' with no content. There is no OpenAPI schema, no response examples, and no description of what the receipt endpoint actually returns. The listing is essentially a stub with confirmed liveness and pricing.
Warnings
- —Documentation pages (docs, API, pricing, README) are all empty beyond a 'Connect wallet' prompt — no usable docs available.
- —The response schema for this endpoint is completely unknown; no examples or field descriptions exist.
- —The specific purpose of 'transaction 115 receipt' is unclear — it may be a demo or placeholder resource.
- —The broader platform advertises many endpoints (AI, finance, utils) but none have documented schemas or examples.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/115/receipt
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform offers endpoints across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/transactions/115/receipt