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 (transaction ID 29) 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/29/receipt` accepts POST requests and returns `application/json`. The x402 challenge confirms the endpoint is live, requiring a maximum payment of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this equals $0.02 per call. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.
Documentation is extremely thin — the /docs, /pricing, /api, and /README pages all resolve to a minimal "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema beyond the x402 output schema stub, and no explanation of what the receipt resource actually contains or what inputs it expects. The platform's landing page lists many endpoints across several categories, but none have detailed documentation available from the crawl.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 29 via a micropayment
- —Demonstrating x402 protocol payment flows on Base
- —Agent-driven per-call API consumption without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base L2
- —Use cases requiring keyless, pay-per-request API access
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based access without crypto wallets
- —Bulk retrieval of multiple transaction receipts (only one transaction ID exposed)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/29/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request body schema, no example responses, and no meaningful documentation beyond a landing page listing. The specific purpose of a 'transaction 29 receipt' is unexplained.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown.
- —All documentation pages (/docs, /pricing, /api, /README) return only a 'Connect wallet' prompt with no content.
- —The endpoint is scoped to a single transaction ID (29); unclear if other transaction IDs are available or what this receipt represents.
- —The broader platform lists many endpoints (AI, finance, utils) but none have verifiable documentation or confirmed liveness beyond this one.
Citations
- —The x402 challenge requires a maximum of 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02.https://lowpaymentfee.com/api/v1/transactions/29/receipt
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) contain only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs