Pay-per-call transaction receipt endpoint on Base via x402, priced at $0.02 in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 370) 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, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/370/receipt` returns a JSON response upon successful payment. The x402 challenge confirms the endpoint is live, accepting exact-scheme payments of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are required — access is granted purely through the x402 payment header.
Documentation on the site is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no example request/response payloads, and no description of what the receipt data actually contains. The platform lists many other endpoints across analytics, AI, finance, and utility categories, but the specific functionality of this transaction receipt endpoint is not documented beyond its title.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 370 via a single paid API call
- —Demonstrating x402 payment-gated API access on Base
- —Integrating pay-per-use receipt retrieval into agent workflows
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents needing on-demand transaction receipt data without API key management
- —Low-volume, pay-as-you-go API consumption on Base
Not for
- —High-volume batch receipt retrieval (no documented bulk endpoints)
- —Users needing detailed documentation or schema guarantees before integration
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/370/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, documentation is effectively absent — no OpenAPI spec, no example payloads, no description of what the receipt contains. The endpoint path references a hardcoded transaction ID (370), making its general utility unclear.
Warnings
- —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content.
- —No OpenAPI or schema available — response format is completely unknown.
- —Endpoint references a specific transaction ID (370); unclear if this is a demo or a fixed resource.
- —No example request or response data available from any source.
Citations
- —Endpoint returns HTTP 402 with x402 challenge accepting USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/370/receipt
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/370/receipt
- —USDC asset address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/370/receipt