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 resource at `/api/v1/transactions/325/receipt`. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The endpoint responds to POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers supply an `X-PAYMENT` header containing a signed payment of up to 20,000 base units of USDC (i.e., $0.02, since USDC uses 6 decimals) to the specified payTo address. No API keys, rate limits, or upfront commitments are required — access is instant once payment is included in the request header.
The specific endpoint probed (`/api/v1/transactions/325/receipt`) appears to serve a receipt for transaction ID 325. The platform's landing page lists many other endpoints (metrics, reports, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, validation, conversion, and generation), all at the same $0.02 price point. Documentation pages beyond the landing page returned only a "Connect wallet" prompt, so detailed request/response schemas for this or other endpoints are not available.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC micropayments
- —Agents autonomously purchasing API access without pre-registered API keys
- —Integrating pay-as-you-go data endpoints into Web3 workflows
Fit
Best for
- —Developers wanting keyless, pay-per-call API access on Base
- —AI agents that need to autonomously pay for API calls via x402
- —Users who prefer crypto micropayments over subscription billing
Not for
- —Users who need free or subscription-based API access
- —Applications requiring detailed OpenAPI documentation or SDK support
- —High-volume batch processing where per-call pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/325/receipt \
-H "X-PAYMENT: <x402-signed-payment>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and all documentation pages beyond the landing page are empty ('Connect wallet' only). The specific purpose of this particular endpoint (transaction 325 receipt) is vague and may be a demo resource.
Warnings
- —No OpenAPI or detailed documentation available — all doc pages return only 'Connect wallet'
- —The endpoint path includes a hardcoded transaction ID (325), suggesting it may be a demo or placeholder resource rather than a general-purpose API
- —No request body schema or response schema is documented anywhere
- —The platform lists many endpoints but none have publicly visible documentation beyond titles and prices
Citations
- —The endpoint returns a 402 challenge requiring USDC payment of 20,000 base units ($0.02) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/325/receipt
- —The platform offers APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categories, all at $0.02 per requesthttps://lowpaymentfee.com
- —No API keys, no rate limits, instant access, Base network settlementhttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/325/receipt