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 (transaction ID 104) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/104/receipt` accepts POST requests and returns an `application/json` response. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header containing a signed payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to the merchant address `0x1A2B…85F3`. The payment scheme is "exact" with a maximum timeout of 300 seconds. No API keys or rate limits are advertised; access is gated purely by micropayment.
The platform's landing page lists 16 endpoints across four categories (Data & Analytics, AI & Machine Learning, Finance & Web3, Infrastructure), all at the same $0.02 price point. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) returned only a "Connect wallet" prompt with no substantive content, so the actual behavior and response schema of this particular receipt endpoint remain undocumented beyond what the x402 challenge reveals.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 104 via micropayment
- —Demonstrating x402 protocol integration for agent-to-service payments
- —Building pay-per-call workflows without API key management
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need to fetch transaction receipts on-demand
- —Projects wanting keyless, pay-as-you-go API access on Base
Not for
- —Users needing detailed API documentation or response schemas before integrating
- —High-volume batch retrieval where per-request fees add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/104/receipt \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payment. However, documentation pages are empty (only 'Connect wallet'), there is no OpenAPI spec, no response schema, and no example responses. The purpose of this specific receipt endpoint is unclear beyond its name. Effectively a stub listing.
Warnings
- —All documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no substantive content
- —No response schema or example response is available for this endpoint
- —The specific purpose and fields of the 'transaction 104 receipt' are undocumented
- —The broader platform lists 16 endpoints but none have documented schemas
Citations
- —The endpoint returns a 402 challenge requiring USDC payment of 20000 base units (0.02 USD) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/104/receipt
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 corresponds to USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/104/receipt
- —Documentation pages returned only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs