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 170) 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/170/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 x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. No API keys or rate limits are required; access is granted purely through on-chain 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 ID 170 via a single micropayment
- —Programmatic access to paid API endpoints without managing API keys or subscriptions
- —Agent-driven workflows that need to fetch financial or transactional data with on-chain settlement
Fit
Best for
- —Developers or agents wanting keyless, pay-per-use API access on Base
- —x402-compatible clients that can settle USDC micropayments automatically
- —Prototyping x402 payment flows at low cost ($0.02/call)
Not for
- —Users needing detailed API documentation or schema definitions before integrating
- —High-volume batch processing where per-request micropayments add friction
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/170/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment on Base to access.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 schema, no request/response examples, and all documentation pages are empty beyond a wallet-connect prompt. The specific purpose of this particular receipt endpoint is unclear, and no input/output structure is documented.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages are all empty
- —No OpenAPI or JSON schema describing request parameters or response format
- —The endpoint is for a specific transaction ID (170); unclear if this is a demo or production resource
- —No information on what data the transaction receipt actually contains
- —Platform lists many API categories (AI, finance, analytics, etc.) but none have documented schemas
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, on Base networkhttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/transactions/170/receipt
- —Platform advertises APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com