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 266) 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/266/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using the "exact" scheme. The endpoint accepts POST requests and returns application/json. The x402 version is 1 with a 300-second payment timeout.
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 API paths but provides no detail on request parameters or response formats for any of them.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 266 via a single micropayment
- —Programmatic access to paid API endpoints without API key management
- —Agent-driven workflows that settle per-call costs in USDC on Base
Fit
Best for
- —Developers wanting keyless, pay-per-use API access on Base
- —AI agents that can settle x402 payments autonomously
- —Users who need transaction receipt data and prefer crypto micropayments
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —High-volume consumers who need bulk pricing or subscription plans
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/266/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof on Base to access the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The specific endpoint (transaction 266 receipt) is narrow and its actual response payload is unknown. The broader platform lists many endpoints but provides zero detail on any of them.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README all render only 'Connect wallet'
- —No OpenAPI or schema definition for request parameters or response format
- —The specific endpoint is for a single transaction receipt (ID 266); unclear if this is a demo or a real resource
- —No information on what fields the receipt response contains
- —The platform lists many API paths on its landing page but none have documented schemas or examples
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/266/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 offers APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs