Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt retrieval API. When called via POST at `/api/v1/transactions/213/receipt`, it returns a JSON receipt for the specified transaction. Payment is handled inline via the x402 protocol: each request costs $0.02 in USDC on the Base network, with no API keys, rate limits, or upfront commitments required.
The endpoint is part of a broader platform (lowpaymentfee.com) that offers a suite of pay-per-call APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints on the platform are priced uniformly at $0.02 per request and settle via USDC on Base.
The specific endpoint listed here (`/api/v1/transactions/213/receipt`) appears to serve a receipt for transaction ID 213. The x402 challenge confirms it is live, accepting the "exact" payment scheme with a maxAmountRequired of 20,000 base units of USDC (6 decimals = $0.02). The payment address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` and the USDC contract is `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base. Documentation beyond the landing page is minimal — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Integrating pay-per-use financial data into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on Base
Fit
Best for
- —Agents or services needing on-demand transaction receipts without subscription overhead
- —Developers exploring x402 protocol integrations on Base
- —Low-volume, pay-as-you-go API consumption
Not for
- —High-volume batch processing where per-call fees add up quickly
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Anyone without access to USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/213/receipt
# Returns 402 with x402 payment challenge.
# Include X-PAYMENT header with a valid x402 payment token (USDC on Base, $0.02) to receive the receipt.Endpoint
Quality
The x402 challenge is live and confirms pricing and payment details, but there is no OpenAPI schema, no response examples, and all documentation pages return only a 'Connect wallet' stub. The specific endpoint path (transaction 213) suggests a hardcoded or demo resource rather than a general-purpose API. Very little can be inferred about the actual response payload.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) contain no substantive content — only a 'Connect wallet' prompt.
- —No OpenAPI or response schema is available; the actual response format is unknown.
- —The endpoint path references a specific transaction ID (213), which may indicate a demo or static resource rather than a general-purpose receipt API.
- —No input schema or request body documentation is provided.
Citations
- —All endpoints on lowpaymentfee.com are priced at $0.02 per request with no API keys, rate limits, or minimums.https://lowpaymentfee.com
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (USD Coin) on Base network.https://lowpaymentfee.com/api/v1/transactions/213/receipt
- —The platform offers APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categories.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/transactions/213/receipt