Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt via a POST request, gated by the x402 payment protocol. It settles on the Base network using USDC (contract 0x8335…2913) with a maximum cost of $0.02 per call (20,000 base units at 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The specific endpoint `/api/v1/transactions/17/receipt` appears to be one resource in a broader platform that offers 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 on the platform are listed at $0.02 per request with the same x402 payment model on Base.
Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the transaction receipt endpoint actually returns. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know the exact request format or response payload without experimentation.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 17 via a single paid API call
- —Programmatic access to transaction data without managing API keys or subscriptions
- —Agent-driven workflows that need on-demand transaction receipts settled in USDC on Base
Fit
Best for
- —Developers wanting zero-setup, pay-per-call access to transaction receipts
- —AI agents that can settle x402 payments autonomously on Base
- —Users who prefer crypto micropayments over traditional API billing
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —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/17/receipt
# Returns 402 with x402 challenge. Attach a valid X-PAYMENT header
# with USDC payment proof on Base to receive the receipt.Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge, but documentation is essentially nonexistent — docs/pricing/API/README pages all show only 'Connect wallet'. No OpenAPI schema, no request/response examples, and the specific purpose of 'transaction 17 receipt' is unclear. The listing is effectively a stub.
Warnings
- —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content
- —No OpenAPI or schema available — request format and response structure are unknown
- —The endpoint path references a specific transaction ID (17); it is unclear whether this is parameterized or fixed
- —The platform lists many other endpoints but none have documented schemas or examples
Citations
- —Endpoint returns HTTP 402 with x402 v1 challenge, accepting USDC on Base with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/transactions/17/receipt
- —Platform lists all endpoints at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/17/receipt