Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com returns a transaction receipt for a given transaction ID (in this case, transaction 200). It is part of a broader suite of pay-per-request APIs offered by the same provider, spanning data analytics, AI/ML inference, finance/Web3 data, and utility services. All endpoints on the platform share the same pricing model: $0.02 per request, paid in USDC on the Base network via the x402 protocol.
The specific endpoint `/api/v1/transactions/200/receipt` accepts POST requests and returns JSON. Payment is handled inline via the X-PAYMENT header using the x402 "exact" scheme. The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, and the maximum amount required is 20,000 base units (i.e., $0.02 given USDC's 6 decimals). There is a 300-second payment timeout. No API keys or rate limits are advertised; access is gated purely by micropayment.
Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload looks like. The endpoint is confirmed live (returns 402 challenge), but the actual functionality and response format must be inferred from the endpoint path alone.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction by ID
- —Programmatic verification or auditing of transaction records
- —Agent-driven workflows that need proof-of-transaction data
Fit
Best for
- —Developers needing simple pay-per-call transaction receipts without signup
- —AI agents that can settle USDC micropayments on Base
- —Use cases where no API key management is desired
Not for
- —Bulk or high-volume receipt retrieval where per-call costs add up
- —Users who need detailed API documentation or guaranteed SLAs before integrating
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/200/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page listing, and no examples. The actual receipt payload structure is unknown. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — response format is unknown
- —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no content
- —The endpoint path is hardcoded to transaction ID 200; it is unclear whether other IDs are supported or what the broader transactions API looks like
- —No rate limit or SLA information provided
Citations
- —Endpoint returns 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/transactions/200/receipt
- —Price is $0.02 per request (20000 base units USDC, 6 decimals)https://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/200/receipt
- —No API keys, no rate limits, instant access advertisedhttps://lowpaymentfee.com
- —Platform offers multiple API categories: Data & Analytics, AI & ML, Finance & Web3, Infrastructurehttps://lowpaymentfee.com