Pay-per-call transaction receipt endpoint on Base via x402, $0.02/request in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt retrieval service behind an x402 paywall. The specific resource `/api/v1/transactions/224/receipt` returns a receipt for transaction ID 224 in JSON format. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) at a cost of $0.02 per request (20000 base units with 6 decimals).
The broader lowpaymentfee.com platform advertises multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities—all priced uniformly at $0.02 per request. The platform emphasizes no API keys, no rate limits, and instant access via x402 payment headers. However, documentation pages beyond the landing page are essentially empty (showing only "Connect wallet"), so the actual behavior and response schemas of these endpoints are undocumented.
The x402 challenge is live and well-formed, confirming the endpoint accepts POST requests and responds with application/json. The payment scheme is "exact" with a max timeout of 300 seconds. No OpenAPI spec, no detailed docs, and no example responses are available from the crawled material.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call payment
- —Demonstrating x402 payment protocol integration on Base
- —Accessing paid API services without API key registration
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless API access via crypto micropayments
- —One-off transaction receipt lookups without subscription commitments
Not for
- —High-volume receipt retrieval where per-call costs add up
- —Users who need detailed API documentation or SDKs
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/224/receipt \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payment. However, there is no OpenAPI spec, no response schema, no example responses, and all documentation pages are empty stubs. The specific purpose of this particular endpoint (transaction 224 receipt) is unclear and may be a demo resource.
Warnings
- —Documentation pages are empty beyond the landing page
- —No response schema or example responses available
- —The endpoint references a specific transaction ID (224) which may be a demo/placeholder
- —Platform legitimacy and actual data returned are unverifiable from available material
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/224/receipt
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/224/receipt