Transaction receipt retrieval via x402 micropayment on Base network, $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource path `/api/v1/transactions/399/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 here returns a receipt for transaction ID 399. The x402 challenge confirms the endpoint is live, accepting POST requests, and requires a maximum payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The response MIME type is application/json.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload looks like. The landing page lists many other endpoints across analytics, AI, finance, and utility categories, but none have documented schemas either. This endpoint appears functional but poorly documented.
Capabilities
Use cases
- —Retrieving a JSON receipt for a specific transaction (ID 399)
- —Programmatic proof-of-payment or audit trail retrieval
- —Agent-driven transaction verification workflows
Fit
Best for
- —Agents needing transaction receipts without API key management
- —Micropayment-based access to transaction data on Base
- —Automated receipt retrieval in Web3 workflows
Not for
- —Bulk transaction history queries (single receipt endpoint only)
- —Users who need detailed API documentation before integrating
- —Free-tier or subscription-based access patterns
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/399/receipt \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation on request parameters, response schema, or what the receipt contains. The /docs, /pricing, and /README pages are all blank beyond a wallet-connect prompt. The endpoint path is hardcoded to a single transaction ID (399), making its general utility unclear.
Warnings
- —No OpenAPI spec or schema documentation available
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —Endpoint path is specific to transaction ID 399 — unclear if other transaction IDs are supported
- —No example request or response payloads available anywhere in crawled material
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The endpoint returns a 402 challenge requiring USDC payment of 20,000 base units ($0.02) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/399/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
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/399/receipt
- —Documentation pages render only a 'Connect wallet' prompt with no additional contenthttps://lowpaymentfee.com/docs