Transaction receipt retrieval via x402 micropayment on Base (USDC, $0.02/request).
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource path `/api/v1/transactions/345/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 and 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 returns a 402 challenge requesting up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using the "exact" scheme with a 300-second timeout. The response MIME type is `application/json`. The endpoint accepts HTTP POST and is marked as discoverable.
Documentation beyond the landing page is extremely thin — 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 example payloads available. The actual content returned after successful payment (i.e., what a "transaction receipt" contains) is not documented anywhere in the crawled material.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 345 via a single micropayment
- —Programmatic access to receipts without API key management
- —Agent-driven workflows that need on-demand paid data retrieval
Fit
Best for
- —Developers wanting keyless, pay-per-use API access on Base
- —AI agents with x402 payment capability needing transaction data
- —Prototyping micropayment-gated API consumption
Not for
- —Bulk or high-volume receipt retrieval (no documented batch endpoint)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/345/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, documentation is essentially nonexistent beyond the landing page — no OpenAPI spec, no request/response schemas, no examples, and the /docs page is empty. The specific resource path (/transactions/345/receipt) is not listed on the homepage and its purpose is only inferable from the URL. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available; /docs, /api, /pricing, /README pages are all blank beyond a wallet-connect prompt
- —The specific endpoint /api/v1/transactions/345/receipt is not listed among the provider's advertised APIs on the landing page
- —No request body schema or response schema is documented — callers cannot know what to send or what they will receive
- —The hardcoded transaction ID '345' in the path suggests this may be a demo or placeholder resource
Citations
- —The endpoint returns a 402 challenge requesting 20,000 base units of USDC on Base ($0.02)https://lowpaymentfee.com/api/v1/transactions/345/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/345/receipt