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 via the x402 payment protocol. The specific path `/api/v1/transactions/21/receipt` returns a receipt for transaction ID 21 in JSON format, gated behind a per-request USDC micropayment on the Base network.
The endpoint is live and returns a standard x402 challenge (HTTP 402) requiring an exact payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 USD (USDC uses 6 decimals). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The method is POST and the response MIME type is application/json.
The broader lowpaymentfee.com platform advertises a suite of x402-gated APIs across categories including Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request. No API keys, rate limits, or commitments are required. However, the specific endpoint being listed here is a transaction receipt resource, and documentation beyond the landing page is essentially empty (all other pages just show a "Connect wallet" prompt), so the actual response schema and detailed behavior are unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt after completing a payment on the platform
- —Programmatic verification of transaction details via receipt lookup
- —Agent-driven workflows that need proof-of-transaction data
Fit
Best for
- —Agents needing pay-per-call access without API key management
- —Micropayment-gated receipt retrieval on Base
- —Developers experimenting with x402 protocol integrations
Not for
- —Bulk or high-volume receipt retrieval where per-call costs add up
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Users who cannot transact in USDC on the Base network
Quick start
# The endpoint requires an x402 payment header. A 402 response returns the challenge:
curl -X POST https://lowpaymentfee.com/api/v1/transactions/21/receipt
# Returns 402 with x402 challenge. Use an x402-compatible client to attach
# the USDC payment header and retry the request.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI schema, no example responses, and no description of what the receipt payload contains. All doc/pricing/API pages beyond the landing page are blank ('Connect wallet' only). The specific endpoint path (transaction 21 receipt) is not mentioned on the landing page, making its purpose unclear.
Warnings
- —No API documentation available — all doc pages return only a 'Connect wallet' prompt
- —No response schema or example response provided for this endpoint
- —The specific endpoint /api/v1/transactions/21/receipt is not listed among the advertised APIs on the landing page
- —Unclear what data the receipt contains or whether transaction ID 21 is a real or demo resource
Citations
- —The endpoint returns a 402 challenge requiring 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/21/receipt
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/21/receipt
- —The platform lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com