x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource via the x402 payment protocol. The specific path `/api/v1/transactions/101/receipt` returns a receipt for transaction 101 in JSON format, gated behind a per-call USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live, accepting POST requests, and requires a maximum of 20,000 base units of USDC (0.02 USD) per call.
lowpaymentfee.com is a broader platform offering multiple x402-gated API categories including 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 minimum commitments required. Payments settle in USDC on the Base L2 network.
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 documentation for what the transaction receipt endpoint actually returns. The endpoint's exact functionality and response structure must be inferred from the path name and the x402 challenge metadata alone.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 101 via a single micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Agent-driven retrieval of financial transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call access to transaction data
- —Projects requiring micropayment-gated API access on Base
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —Bulk retrieval of many transaction receipts (no batch endpoint evident)
- —Users who cannot pay in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/101/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation, no OpenAPI schema, no request/response examples, and the docs pages are empty. The endpoint's actual response structure is unknown, making this effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — response format is entirely unknown
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —The specific endpoint path (/transactions/101/receipt) suggests a hardcoded resource; it is unclear whether other transaction IDs are supported
- —No request body schema or response examples are available anywhere in the crawl
Citations
- —The x402 challenge returns 402 with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/101/receipt
- —All endpoints 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 APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/101/receipt