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 access to a transaction receipt resource (transaction ID 391) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme. The price per call is $0.02 (20,000 base units with 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (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 scoped to `/api/v1/transactions/391/receipt`, which appears to return a receipt for a particular transaction.
Documentation is extremely sparse — 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 describing what the receipt payload contains or what input parameters the POST body expects. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the lack of documentation makes it difficult to use without experimentation.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction (ID 391) via programmatic pay-per-call access
- —Demonstrating x402 payment protocol integration for agent-to-agent commerce
- —Testing USDC micropayment flows on the Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access without API key management
- —Use cases requiring USDC-settled micropayments on Base
Not for
- —Users needing detailed API documentation or response schema before integrating
- —Bulk or high-volume receipt retrieval across many transaction IDs
- —Anyone requiring non-crypto payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/391/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is confirmed live with a valid 402 x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the endpoint path is specific to a single transaction ID (391), making its general utility unclear.
Warnings
- —No documentation available — docs, API, pricing, and README pages all render only 'Connect wallet'
- —No OpenAPI or output schema describing the response format
- —Endpoint is scoped to a single transaction ID (391); unclear if other transaction IDs are available or how to discover them
- —No request body schema documented; unknown what POST body parameters are expected
- —Platform advertises many endpoints but none have detailed docs
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/391/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com