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/102/receipt` returns a JSON receipt when a valid USDC micropayment is made on the Base network. The x402 challenge confirms the endpoint is live, accepting POST requests with an exact payment scheme.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call 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 $0.02 per request, settled in USDC on the Base network. The platform emphasizes no API keys, no rate limits, and instant access.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The x402 challenge for this specific endpoint shows a maxAmountRequired of 20000 base units of USDC (6 decimals), which equals $0.02. The payTo address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` and the asset contract is the canonical Base USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`).
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 102 via micropayment
- —Programmatic access to receipts without API key registration
- —Agent-driven payment-gated data retrieval on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need pay-per-call access without pre-registration
- —Use cases requiring USDC micropayments on Base L2
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based API access
- —High-volume batch retrieval where per-call pricing is inefficient
Quick start
# 1. Send a POST to get the 402 challenge:
curl -X POST https://lowpaymentfee.com/api/v1/transactions/102/receipt
# 2. Parse the 402 response, construct an X-PAYMENT header with a signed USDC payment of 20000 base units ($0.02) on Base, then resend:
curl -X POST -H "X-PAYMENT: <signed_payment_token>" https://lowpaymentfee.com/api/v1/transactions/102/receiptEndpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation on request parameters, response schema, or what data the receipt actually contains. All doc pages return only 'Connect wallet' with no technical content. No OpenAPI spec is available.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet'
- —No OpenAPI or schema definition for request or response payloads
- —The specific endpoint path (/transactions/102/receipt) suggests a hardcoded resource; unclear if other transaction IDs are supported
- —Purpose and contents of the 'receipt' response are undocumented
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/102/receipt
- —All endpoints listed at $0.02 per request with no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/102/receipt
- —Platform offers APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com