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 for transaction ID 121 via a POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced uniformly at $0.02 per request with no API keys, no rate limits, and no commitments required.
The specific endpoint `/api/v1/transactions/121/receipt` returns a JSON response upon payment of up to 20,000 base units of USDC (0x8335…2913) on the Base network, which equals $0.02 USD (USDC uses 6 decimals). Payment is handled via the x402 protocol's "exact" scheme: callers include an X-PAYMENT header with a signed payment proof, and the server validates it before returning the receipt data. The payment is directed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The platform's landing page advertises a wide catalog of endpoints across analytics, AI inference (sentiment analysis, summarization, classification, embeddings), financial data (price feeds, exchange rates, token quotes, gas estimates), and utility services (geocoding, validation, conversion, generation), all at the same $0.02 price point. However, documentation pages beyond the landing page returned only a "Connect wallet" prompt with no substantive content, so the actual behavior, input parameters, and response schemas for this and other endpoints remain undocumented in the crawled material.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 121 via programmatic pay-per-call access
- —Demonstrating x402 protocol integration for USDC micropayments on Base
- —Agent-driven workflows that need on-demand paid data retrieval without pre-registration
Fit
Best for
- —Developers experimenting with x402 protocol payments on Base
- —Agents needing keyless, pay-per-call API access settled in USDC
- —Low-friction access to transaction receipts without subscription overhead
Not for
- —Bulk or high-volume receipt retrieval where per-call pricing adds up
- —Users who need detailed API documentation or OpenAPI schemas before integrating
- —Non-crypto users who cannot pay with USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/121/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documented request/response format, no examples, and all documentation pages returned only 'Connect wallet' with no content. The specific endpoint path (transactions/121/receipt) is hardcoded to a single transaction ID, which limits general utility. Effectively a stub listing.
Warnings
- —No API documentation available — all doc pages return only 'Connect wallet' with no content
- —No OpenAPI or JSON schema describing request parameters or response format
- —The endpoint path is hardcoded to transaction ID 121; it is unclear if other transaction IDs are supported or how to discover them
- —The platform advertises many endpoint categories but none were verified beyond the landing page listing
- —Response body structure is completely unknown — no examples available
Citations
- —The endpoint returns HTTP 402 with x402 challenge requiring up to 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/121/receipt
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/121/receipt
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers endpoints across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com