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/98/receipt` returns a receipt for transaction ID 98 in JSON format, gated behind a per-call USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live and accepts exact-scheme payments of up to 20,000 base units of USDC (0.02 USD) per request.
The broader lowpaymentfee.com platform advertises a suite of x402-gated APIs spanning data & analytics (metrics, reports, data export, insights), AI & ML (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. 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 technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available from the crawl. The specific behavior of the `/transactions/98/receipt` endpoint (what fields it returns, what inputs it expects beyond POST) is unknown beyond the x402 challenge metadata.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 98 via a single micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need to fetch transaction receipts with crypto micropayments
- —Projects requiring keyless, pay-per-use API access on Base
Not for
- —Production use requiring documented request/response schemas
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need fiat-only payment rails
Quick start
# 1. POST to the endpoint — you'll get a 402 with payment challenge
curl -X POST https://lowpaymentfee.com/api/v1/transactions/98/receipt
# 2. Parse the 402 JSON, pay 20000 base-units USDC on Base to the payTo address,
# then re-POST with the X-PAYMENT header containing your payment proof.Endpoint
Quality
The x402 challenge is live and confirms pricing and network, but there is zero documentation on request parameters, response schema, or what the receipt actually contains. The docs pages are empty stubs. This is effectively a stub listing with a verified payment gate.
Warnings
- —No OpenAPI spec or schema documentation available
- —All documentation pages (/docs, /api, /pricing, /README) return only a 'Connect wallet' prompt with no content
- —The specific endpoint path references a hardcoded transaction ID (98); it is unclear whether this is a demo or a real resource
- —No request body schema or response body schema is documented anywhere
- —The broader platform lists many endpoints but none have documented behavior beyond a title and price
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/98/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs