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. The specific resource `/api/v1/transactions/377/receipt` returns a receipt for transaction ID 377 in JSON format. Payment is handled inline via the x402 protocol: callers attach a USDC payment on the Base network in the `X-PAYMENT` header, and the endpoint responds with the requested data. The price is $0.02 per request (20,000 base units of USDC with 6 decimals).
The broader lowpaymentfee.com platform advertises a wide catalog 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 with no API keys, no rate limits, and no minimum commitments required. Payment settles on the Base L2 network in USDC.
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 schema, no request/response examples, and no explanation of what fields the receipt object contains or what input parameters are expected. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the lack of documentation makes it difficult to use without experimentation.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Agent-driven workflows that need verifiable transaction data without subscription overhead
- —Integrating pay-as-you-go receipt lookups into Web3 applications
Fit
Best for
- —Developers wanting zero-commitment, pay-per-call access to transaction receipts
- —AI agents that can settle x402 payments on Base in USDC
- —Projects needing no-API-key access to financial data endpoints
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —High-volume batch retrieval where per-call pricing becomes expensive
- —Non-crypto workflows that cannot settle payments on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/377/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge and clear pricing ($0.02 USDC on Base). However, documentation is essentially nonexistent — no OpenAPI schema, no request/response examples, no field descriptions. The specific endpoint path (/transactions/377/receipt) suggests a fixed resource rather than a parameterized API, and the broader platform's many advertised endpoints lack any technical detail beyond names and prices.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no usable content
- —No OpenAPI or schema available — request parameters and response shape are unknown
- —The endpoint path includes a hardcoded transaction ID (377); it is unclear how to query other transactions
- —The broad catalog of 16+ endpoints (AI, finance, utilities) all at identical $0.02 pricing with no documentation raises questions about actual functionality
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/377/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform advertises APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/377/receipt