x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 167) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network via the x402 protocol.
The specific endpoint probed (/api/v1/transactions/167/receipt) returns a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the site's advertised pricing. Payment is made via the "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. No API keys or rate limits are required; access is granted purely through x402 payment.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the transaction receipt contains or what input parameters are accepted. The endpoint accepts POST requests and returns application/json, but the actual payload structure is unknown.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction 167 via a single micropayment
- —Programmatic access to receipt information without API key management
- —Agent-driven workflows that need to fetch financial transaction records on-demand
Fit
Best for
- —Developers wanting keyless, pay-per-use API access on Base
- —AI agents that can settle x402 payments in USDC
- —Use cases requiring low-friction access to transaction receipts
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —Bulk retrieval of many transaction receipts (only transaction 167 is exposed at this endpoint)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/167/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI schema, no documentation, no request/response examples, and the purpose of this specific receipt endpoint is unclear. The broader site lists many APIs but provides no substantive docs for any of them.
Warnings
- —No OpenAPI schema or machine-readable API documentation available
- —All documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompt with no content
- —The specific endpoint is scoped to a single transaction ID (167); unclear if other transaction IDs are available
- —No request body schema or response schema is documented anywhere
- —The broader platform advertises many endpoints but none have verifiable documentation
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/167/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform advertises APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimalshttps://lowpaymentfee.com/api/v1/transactions/167/receipt