Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt for transaction ID 195 via the x402 payment protocol. It is part of a broader platform (lowpaymentfee.com) that offers a suite of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all settled on the Base network using USDC.
The specific endpoint `/api/v1/transactions/195/receipt` accepts POST requests and returns a JSON response upon payment. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 USD (USDC uses 6 decimals). The platform's landing page confirms a flat $0.02 per request across all endpoints, with no API keys, no rate limits, and instant access.
However, this particular endpoint appears to be a single-resource receipt retrieval (transaction 195), and it is unclear what the receipt contains or what broader transaction system it belongs to. The platform's documentation pages (docs, pricing, README) all render only a "Connect wallet" prompt with no substantive content, so there is no schema documentation, example payloads, or detailed API reference available. The endpoint is live and returning a valid x402 402 challenge.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 195 via programmatic payment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agent-driven receipt fetching settled in USDC on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing to fetch transaction receipts with crypto micropayments
- —Use cases requiring no-signup, no-API-key access
Not for
- —Bulk transaction receipt retrieval (single hardcoded transaction ID)
- —Users who need detailed API documentation or schema references
- —Production systems requiring SLA guarantees or documented error handling
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/195/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, and the landing page confirms pricing. However, the endpoint is for a single hardcoded transaction ID (195) with no documentation on what it returns, no request/response schema, and all doc pages are empty. The purpose and utility of this specific receipt endpoint are unclear.
Warnings
- —All documentation pages (/docs, /pricing, /README, /api) render only 'Connect wallet' with no content
- —Endpoint is scoped to a single transaction ID (195) — unclear if this is a demo or production resource
- —No request or response schema available; no examples of what the receipt contains
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/195/receipt
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/195/receipt