x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 174) 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 (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, with no API keys, no rate limits, and no minimum commitments.
The specific endpoint probed (`/api/v1/transactions/174/receipt`) returns a valid x402 challenge (HTTP 402) requesting up to 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 via the x402 "exact" scheme, with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
Documentation is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The platform's actual API functionality behind the paywall cannot be verified from the crawl alone.
Capabilities
Use cases
- —Retrieving transaction receipts via micropayment-gated API calls
- —Programmatic access to paid data endpoints without API key management
- —Agent-driven workflows that need on-demand paid API access on Base
Fit
Best for
- —Developers wanting keyless, pay-per-call API access
- —AI agents that can settle x402 payments in USDC on Base
- —Use cases requiring low-friction micropayment-gated endpoints
Not for
- —Users needing detailed API documentation or OpenAPI specs before purchasing
- —High-volume batch processing where per-call pricing may add up
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/174/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid USDC payment proof to access the receipt.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 request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The specific purpose of 'transaction 174 receipt' is opaque. The listing is essentially a stub with confirmed liveness.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema describing request parameters or response format
- —The specific resource '/api/v1/transactions/174/receipt' is a single hardcoded transaction ID; unclear if this generalizes
- —Platform advertises many endpoints but none have documented schemas or verifiable functionality
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge requests maxAmountRequired of 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02https://lowpaymentfee.com/api/v1/transactions/174/receipt
- —Platform offers APIs across data & analytics, AI/ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com