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 provides a "Premium API Access" receipt for transaction ID 320. It is part of a broader platform offering numerous pay-per-call APIs spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments required.
The specific endpoint `/api/v1/transactions/320/receipt` accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) via the x402 "exact" scheme. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. The payment is directed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds.
Documentation on the site 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 schema, no request/response examples, and no detailed description of what the receipt endpoint actually returns. The platform advertises many other endpoints (sentiment analysis, summarization, geocoding, etc.) at the same $0.02 price point, but without documentation it is unclear what data or functionality each provides.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 320 via a single paid API call
- —Demonstrating x402 payment protocol integration for agent-to-agent commerce
- —Testing low-cost micropayment workflows on Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access without API key management
- —Low-cost micropayment API consumption on Base/USDC
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk transaction receipt retrieval across many transaction IDs
- —Users who need fiat-only payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/320/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (returns 402 with a valid x402 challenge), and pricing is clear at $0.02 USDC on Base. However, there is no OpenAPI schema, no documentation, no request/response examples, and the purpose of this specific receipt endpoint is unclear. The docs pages are empty beyond a wallet-connect prompt.
Warnings
- —No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or schema definition for request or response payloads
- —The specific endpoint is for a hardcoded transaction ID (320); unclear if other transaction IDs are supported or what the receipt contains
- —Platform advertises many endpoints but none have documented behavior
Citations
- —The endpoint returns HTTP 402 with x402 challenge requiring 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/320/receipt
- —All APIs priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/320/receipt
- —Platform offers endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com