Transaction receipt retrieval via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource path `/api/v1/transactions/376/receipt`) behind an x402 paywall. Payment is settled in USDC on the Base network at $0.02 per request (20,000 base units with 6 decimals). The endpoint accepts POST requests and returns JSON.
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 priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing is for the transaction receipt endpoint only.
Documentation on the site 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 receipt payload contains or what input the POST body expects. The endpoint is confirmed live via a valid x402 402 challenge.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction via programmatic API call
- —Integrating pay-per-call receipt lookups into agent workflows without API key management
- —Demonstrating x402 protocol micropayment flows on Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call access to transaction data
- —Projects requiring low-friction micropayment API integration on Base
Not for
- —Bulk or high-volume receipt retrieval (no documented batch endpoint)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Non-crypto workflows that cannot settle USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/376/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no request/response examples, and the docs pages are empty. The purpose of this specific receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —No request body schema or response schema documented — unclear what POST body is expected or what the receipt contains
- —This endpoint is for a single hardcoded transaction ID (376); unclear if it generalizes
Citations
- —Endpoint returns x402 402 challenge with maxAmountRequired 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/376/receipt
- —Platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/376/receipt