x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource behind an x402 paywall. It is part of a broader platform that advertises multiple API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/59/receipt` returns a receipt for transaction ID 59. The x402 challenge confirms the endpoint is live, accepting POST requests, and requires a payment of up to 20,000 base units of USDC (0x8335…) on Base. Since USDC uses 6 decimals, this translates to $0.02 per call — consistent with the platform's advertised flat pricing. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation is extremely thin: the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 outputSchema stub, and no examples of what the receipt payload actually contains. The platform markets itself as requiring no API keys and no rate limits, with instant access via the x402 payment protocol.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID via programmatic payment
- —Demonstrating x402 pay-per-call integration on the Base network
- —Agents that need to fetch financial transaction data without pre-registration
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents needing no-signup, pay-per-call transaction data
- —Prototyping micropayment-gated API workflows on Base
Not for
- —Production use requiring documented response schemas and SLAs
- —Bulk retrieval of many transaction receipts (no batch endpoint visible)
- —Users who need fiat-only payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/59/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but documentation is effectively nonexistent — every doc page returns only 'Connect wallet'. There is no OpenAPI spec, no response schema, and no examples of what the receipt payload contains. The endpoint path is specific to transaction ID 59, making it unclear how generalizable this is.
Warnings
- —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content.
- —No OpenAPI or response schema available — the actual receipt payload structure is unknown.
- —The endpoint path is hardcoded to transaction ID 59; it is unclear whether other transaction IDs are supported or how to discover them.
- —The broader platform advertises many API categories (AI, analytics, finance, utilities) but none could be verified beyond the landing page listings.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/59/receipt
- —Platform advertises $0.02 per request flat pricing with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/59/receipt
- —Platform lists API categories including Data & Analytics, AI & ML, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com