Pay-per-call transaction receipt endpoint on Base via x402, priced at $0.02 in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" receipt resource for transaction ID 215. It is part of a broader platform offering dozens of pay-per-request API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all settled on the Base network using USDC at $0.02 per request via the x402 payment protocol.
The specific endpoint `/api/v1/transactions/215/receipt` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring an exact payment of 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base, 6 decimals = $0.02) to wallet 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. No API keys are needed; payment is the authentication. The platform advertises no rate limits and instant access.
Documentation 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 spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The endpoint's purpose (retrieving a transaction receipt) is inferred from the URL path and the generic "Premium API Access" description. The broader platform lists many endpoints but provides no detailed documentation for any of them.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 215 via a single paid API call
- —Programmatic access to receipt data without managing API keys or subscriptions
- —Agent-driven workflows that need to fetch financial transaction records on demand
Fit
Best for
- —Developers wanting keyless, pay-per-use API access settled in USDC on Base
- —AI agents that can handle x402 payment challenges natively
- —Users who need a single transaction receipt without committing to a subscription
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/215/receipt
# Returns 402 with x402 payment challenge.
# Include X-PAYMENT header with a signed USDC payment on Base to complete the request.Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no OpenAPI spec, no request/response examples, and the specific purpose of this single-resource endpoint (transaction 215 receipt) is unclear. The broader platform pages are empty beyond wallet-connect prompts.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content.
- —No OpenAPI or schema definition found; request body and response format are completely unknown.
- —This endpoint is for a specific resource (transaction 215 receipt); it is unclear if it generalizes to other transaction IDs.
- —The platform lists many endpoints on its homepage but provides zero documentation for any of them.
Citations
- —The endpoint returns a 402 challenge requiring 20,000 base units of USDC on Base (= $0.02)https://lowpaymentfee.com/api/v1/transactions/215/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/215/receipt
- —Platform advertises $0.02/request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com