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 "Premium API Access" transaction receipt resource. When called via POST at `/api/v1/transactions/250/receipt`, it returns a JSON receipt for transaction ID 250. Payment is handled inline via the x402 protocol: callers attach an X-PAYMENT header with a USDC payment on the Base network. The price per request is $0.02 (20,000 base units of USDC with 6 decimals).
The provider's landing page advertises a broader suite of endpoints 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 priced uniformly at $0.02 per request. No API keys or rate limits are advertised; access is instant via x402 payment on the Base L2 network.
Documentation is extremely sparse — the /docs, /pricing, /api, 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 usage examples available from the crawl. The specific endpoint probed (`/api/v1/transactions/250/receipt`) is live and returns a valid x402 402 challenge, but what exactly the receipt payload contains is unknown.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC payment
- —Integrating pay-as-you-go API access into agent workflows without API key management
- —Accessing financial or transactional data via x402 protocol on Base L2
Fit
Best for
- —Agents or applications that need keyless, pay-per-call API access
- —Developers building on Base network who want frictionless micropayment APIs
- —Workflows requiring transaction receipt retrieval with no subscription commitment
Not for
- —Users who need detailed API documentation or response schema guarantees before integrating
- —High-volume use cases where per-request pricing at $0.02 may be cost-prohibitive compared to subscription APIs
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/250/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 it works. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The specific purpose of this particular receipt endpoint is unclear beyond the generic 'Premium API Access' label.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all render only 'Connect wallet'
- —No OpenAPI or schema definition found; request and response formats are unknown
- —The specific data returned by /api/v1/transactions/250/receipt is undocumented
- —The broader suite of advertised endpoints (AI, analytics, finance, utils) could not be verified beyond the landing page listing
Citations
- —The endpoint returns a valid x402 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/250/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 provider advertises endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs