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 239) 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/239/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this equates to $0.02 per call, consistent with the site's advertised pricing. Payment is made via the x402 "exact" scheme, requiring no API keys, no rate limits, and no upfront commitments — just a valid X-PAYMENT header with each request.
Documentation is extremely sparse. 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 examples of what the receipt payload actually contains. The platform's landing page lists many endpoint paths but provides no detail on input parameters or response formats for any of them. The specific transaction receipt endpoint's purpose and output structure are unknown beyond the mimeType of application/json.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 239 via a single micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to fetch transaction receipts with per-call USDC payments
- —Projects requiring keyless, pay-as-you-go API access
Not for
- —Users needing detailed API documentation or response schema before integrating
- —Bulk retrieval of many different transaction receipts (only transaction 239 is exposed at this path)
- —Users who cannot pay in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/239/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"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 documentation beyond a landing page listing, no request/response examples, and no explanation of what the receipt endpoint actually returns. The docs pages are empty. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for any endpoint on the platform
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The specific endpoint is for a single hardcoded transaction ID (239); unclear if other transaction IDs are available
- —No response schema or example output is documented anywhere
- —The platform lists many endpoints on its landing page but none have documented input/output contracts
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/239/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/239/receipt
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages render only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs