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 132) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI/ML (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 via the x402 protocol. No API keys, rate limits, or commitments are required.
The specific probed endpoint (`/api/v1/transactions/132/receipt`) accepts POST requests and returns `application/json`. The x402 challenge confirms it is live, requesting up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call, paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The payment timeout is 300 seconds.
Documentation is extremely sparse — the /docs, /pricing, /api, 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 examples of what the receipt payload actually contains. The platform's landing page lists many endpoints but provides no detail on request parameters or response formats for any of them.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 132 via a single paid API call
- —Programmatic access to paid data endpoints without API key management
- —Agent-driven workflows that settle per-request costs in USDC on Base
Fit
Best for
- —Developers wanting zero-signup, pay-per-use API access
- —AI agents with x402-compatible wallets on Base
- —Use cases requiring no rate limits or subscription commitments
Not for
- —Users needing detailed API documentation or response schema guarantees before integrating
- —High-volume batch processing where per-request pricing may add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/132/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment proof to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI spec, no documentation beyond a landing page listing, no request/response examples, and the docs pages are empty. The specific purpose of this 'transaction receipt' endpoint is unclear, making this effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request parameters and response format are unknown.
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content.
- —The specific endpoint path references a hardcoded transaction ID (132); it is unclear whether this is a general-purpose receipt endpoint or a single fixed resource.
- —The platform lists many endpoints on its landing page but provides no detail on any of them — actual functionality is unverified.
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Base (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913).https://lowpaymentfee.com/api/v1/transactions/132/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The platform lists APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categories.https://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) contain only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs