Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" transaction receipt resource. When called via POST at `/api/v1/transactions/400/receipt`, it returns a JSON response after receiving a valid x402 payment header. The endpoint settles on the Base network using USDC (contract 0x8335…2913) with a maximum amount of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). No API keys or rate limits are required — access is gated purely by micropayment.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs across four categories: 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 $0.02 per request with the same x402 payment model on Base.
This specific endpoint (`/api/v1/transactions/400/receipt`) appears to serve transaction receipt data, though the exact response schema is not documented. The probe confirms the endpoint is live, returning a proper 402 challenge with x402 version 1. Documentation pages on the site are minimal — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail.
Capabilities
Use cases
- —Retrieving transaction receipt data for a specific transaction ID via micropayment
- —Integrating pay-per-call receipt lookups into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on the Base network
Fit
Best for
- —Agents needing on-demand transaction receipts without subscription commitments
- —Developers exploring x402 micropayment-gated APIs
- —Low-volume or sporadic access patterns where per-call pricing is economical
Not for
- —High-volume bulk transaction data retrieval where subscription pricing would be cheaper
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto-native consumers who cannot produce x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/400/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no documentation of the request body, response schema, or what 'transaction 400 receipt' actually returns. The docs/pricing/README pages are all blank beyond a wallet connect prompt. This is effectively a stub listing with minimal usable information.
Warnings
- —No response schema or example response documented anywhere
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no technical content
- —The specific purpose of /api/v1/transactions/400/receipt is unclear — it may be a demo or placeholder endpoint
- —No OpenAPI spec or machine-readable schema available
Citations
- —Endpoint returns 402 with x402 version 1 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/400/receipt
- —maxAmountRequired is 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02https://lowpaymentfee.com/api/v1/transactions/400/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com