Transaction receipt retrieval via x402 micropayment on Base network, $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource `/api/v1/transactions/244/receipt`) behind an x402 paywall. The provider operates a broad suite of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network. No API keys, rate limits, or upfront commitments are required; callers simply attach an x402 payment header to each request.
The specific endpoint probed here returns a receipt for transaction ID 244. The x402 challenge confirms the endpoint is live, accepting POST requests with an exact-scheme payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment timeout is 300 seconds. The response MIME type is `application/json`.
Documentation beyond the landing page is sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no example request/response payloads, and no description of the receipt's JSON schema. The provider's landing page lists many other endpoints across analytics, AI, finance, and utility categories, all at the same $0.02 price point, but none include detailed documentation either.
Capabilities
Use cases
- —Retrieving a JSON receipt for a specific transaction via micropayment
- —Programmatic access to transaction data without API key registration
- —Agent-driven workflows that need proof-of-transaction receipts
Fit
Best for
- —Agents or scripts that need on-demand transaction receipts without signup
- —Developers exploring x402 payment-gated API patterns
- —Low-volume, pay-as-you-go access to transaction data
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Production systems requiring SLA guarantees or support
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/244/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no example payloads, and all secondary pages render only a wallet-connect prompt. The specific purpose of this receipt endpoint is unclear beyond its URL path.
Warnings
- —No OpenAPI or schema documentation available — response format is unknown
- —All documentation pages (/docs, /pricing, /api, /README) return only a 'Connect wallet' prompt with no technical content
- —The endpoint is for a specific transaction ID (244); it is unclear whether other transaction IDs are accessible or what the receipt contains
- —Provider lists many endpoints on the landing page but none have detailed docs
Citations
- —Endpoint returns x402 challenge with maxAmountRequired 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/244/receipt
- —All APIs priced at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/244/receipt