x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource via the x402 payment protocol. The specific path `/api/v1/transactions/22/receipt` returns a receipt for transaction ID 22 in JSON format, gated behind a per-request USDC micropayment on the Base network.
The broader lowpaymentfee.com platform advertises a suite of x402-protected APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (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 a uniform $0.02 per request, paid in USDC on Base. The platform emphasizes no API keys, no rate limits, and instant access — callers simply attach an x402 payment header to each request.
The probed endpoint returns a valid x402 challenge (HTTP 402) with `maxAmountRequired` of 20000 base units of USDC (0x8335… on Base, 6 decimals), which equals $0.02. The payment scheme is "exact" with a 300-second timeout. No OpenAPI schema, detailed documentation, or example responses were found in the crawl — the docs, pricing, API, and README pages all rendered only a "Connect wallet" prompt with no substantive content.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID via micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call receipt retrieval without signup
- —Low-volume, on-demand transaction receipt lookups
Not for
- —Bulk or high-volume receipt retrieval (no documented batch support)
- —Users who need detailed API documentation or response schema guarantees
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/22/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 there is no OpenAPI schema, no example responses, and no meaningful documentation — all doc pages render only a wallet-connect prompt. The specific endpoint path (/transactions/22/receipt) is hardcoded to a single transaction ID, and its utility beyond a demo is unclear.
Warnings
- —No OpenAPI or schema documentation available; response format is unknown beyond mimeType application/json.
- —All documentation pages (docs, pricing, API, README) render only a 'Connect wallet' prompt with no substantive content.
- —The endpoint path is hardcoded to transaction ID 22; it is unclear whether other transaction IDs are supported or what data the receipt contains.
- —The broader platform lists many API categories (AI, finance, analytics, infrastructure) but none could be verified beyond their listing on the homepage.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/22/receipt
- —All endpoints are listed at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform advertises APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/22/receipt