Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt retrieval API gated by the x402 payment protocol. When called via POST, it returns a JSON receipt for a given transaction (identified by ID in the URL path). Payment is settled on the Base network using USDC (contract 0x8335…2913) with an exact-scheme challenge requiring up to 20,000 base units (i.e., $0.02 given USDC's 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data & analytics (metrics, reports, data export, insights), AI & ML (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available from the crawl. The specific endpoint probed (/api/v1/transactions/123/receipt) is live and returns a valid x402 402 challenge, but its actual response payload structure is unknown.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC micropayments
- —Integrating pay-as-you-go API access into agent workflows without API key management
- —Fetching financial transaction data on-demand via crypto-native payment rails
Fit
Best for
- —Agents or services that need on-demand transaction receipt retrieval without subscription overhead
- —Developers building on Base who want USDC-settled API access
- —Scenarios requiring keyless, permissionless API consumption
Not for
- —High-volume batch processing where per-call pricing becomes expensive
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Users without access to USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/123/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The actual functionality behind the receipt endpoint is unverifiable beyond the challenge metadata.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all render only 'Connect wallet'
- —No OpenAPI or schema definition found; request and response formats are unknown
- —The specific endpoint path includes a hardcoded transaction ID (123), suggesting it may be a demo or placeholder
- —The platform lists many endpoints (AI, finance, utils) but none have documented schemas or verifiable functionality
Citations
- —The endpoint returns a valid x402 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/123/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs