Transaction receipt retrieval via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource `/api/v1/transactions/327/receipt`) behind an x402 paywall. The provider operates a broad suite of pay-per-call APIs 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. No API keys, rate limits, or commitments are required — callers simply attach an x402 payment header to each request.
The specific endpoint probed here returns a receipt for transaction ID 327. Based on the x402 challenge, the maximum amount required is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`.
Note that while the provider's landing page advertises many other endpoints (sentiment analysis, text summarization, embeddings, price feeds, geocoding, etc.), this listing covers only the `/api/v1/transactions/327/receipt` endpoint. Documentation beyond the landing page is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID
- —Programmatic proof-of-transaction retrieval for auditing or record-keeping
- —Agent-driven payment-gated data access on Base network
Fit
Best for
- —Developers needing low-cost, keyless API access settled in USDC on Base
- —AI agents that can handle x402 payment challenges natively
- —Quick one-off transaction receipt lookups without subscription overhead
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/327/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no request/response schema, no example payloads, and the docs pages are empty. The specific purpose of this receipt endpoint (transaction 327) is narrow and undocumented. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown.
- —Docs, API, pricing, and README pages all render only 'Connect wallet' with no usable content.
- —This endpoint is scoped to a single transaction ID (327); it is unclear whether other transaction IDs are accessible or how they are discovered.
- —The broader API suite advertised on the landing page (AI, analytics, finance, utils) could not be verified beyond the homepage listing.
Citations
- —The x402 challenge requires a maximum of 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02.https://lowpaymentfee.com/api/v1/transactions/327/receipt
- —The provider advertises $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The provider lists endpoints for analytics, AI/ML, finance/Web3, and infrastructure utilities.https://lowpaymentfee.com
- —Docs, API, pricing, and README pages render only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs