x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 165) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/165/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The challenge advertises a max amount of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The platform markets itself as requiring no API keys, no rate limits, and no commitments — just per-request micropayments. Documentation pages (/docs, /pricing, /api, /README) all appear to require a wallet connection and contain no additional rendered content in the crawl. As a result, the actual response schema, detailed field descriptions, and deeper documentation are unavailable, making it difficult to assess what data the receipt endpoint actually returns.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 165 via a micropayment
- —Demonstrating x402 protocol integration for agent-to-service payments
- —Programmatic access to paid receipt data without traditional API key management
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need to fetch transaction receipts on-demand
- —Projects wanting keyless, pay-per-use API access on Base
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation before integrating
- —Applications requiring free or subscription-based access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/165/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, there is no OpenAPI schema, no response examples, and all documentation pages render only a wallet-connect prompt with no useful content. The specific purpose of a 'transaction 165 receipt' is unclear, and no input/output schemas are available.
Warnings
- —All documentation pages (/docs, /pricing, /api, /README) render only a wallet-connect prompt — no actual docs are available from the crawl.
- —The endpoint path references a specific transaction ID (165); it is unclear whether this is a generic pattern or a single fixed resource.
- —No response schema or example response is available; the actual data returned is unknown.
- —The broader platform lists many API categories (AI, finance, analytics, utilities) all at $0.02, but none have documented schemas — the platform may be a demo or early-stage project.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/165/receipt
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/165/receipt
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and no commitmentshttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com