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/368/receipt` returns a receipt for transaction ID 368 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 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 not documented.
The x402 challenge is live and well-formed, confirming the endpoint accepts POST requests and returns application/json. The payment timeout is 300 seconds. No OpenAPI spec or detailed documentation is available, making it difficult to know what request body (if any) is expected or what the receipt response structure looks like.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID
- —Programmatic access to payment confirmation data without API key management
- —Agent-driven workflows that need proof-of-transaction documents
Fit
Best for
- —Agents needing transaction receipts without pre-registration
- —Developers testing x402 payment flows on Base
- —Low-friction pay-per-use API access
Not for
- —Bulk transaction history retrieval (single-receipt endpoint)
- —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/368/receipt \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no documentation of request/response schemas, and all doc pages are empty stubs. The endpoint's actual functionality (what data the receipt contains, what inputs are needed) is entirely undocumented.
Warnings
- —No OpenAPI or schema documentation available
- —All documentation pages (docs, api, pricing, README) are empty beyond a wallet-connect prompt
- —Request body schema and response structure are unknown
- —This appears to be a single hardcoded transaction ID (368); unclear if other IDs are accessible
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/368/receipt
- —Price is $0.02 per request across all endpointshttps://lowpaymentfee.com
- —Platform advertises no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/368/receipt