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 path `/api/v1/transactions/179/receipt`) behind an x402 paywall. Payment is settled in USDC on the Base network at $0.02 per request (maxAmountRequired of 20,000 base units with USDC's 6 decimals). The endpoint accepts POST requests and returns JSON.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto market data, and infrastructure utilities — all priced uniformly at $0.02 per request. The platform emphasizes no API keys, no rate limits, and instant access via the x402 protocol.
However, this specific endpoint (`/api/v1/transactions/179/receipt`) appears to serve a transaction receipt for a particular transaction ID (179), which is a narrow resource rather than a general-purpose API. Documentation beyond the landing page is essentially empty (all subpages just show "Connect wallet"), so the exact schema of the receipt response, supported parameters, and the nature of the returned data are unknown. The endpoint is confirmed live via a valid 402 challenge.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction via micropayment
- —Demonstrating x402 protocol payment flow on Base network
- —Programmatic access to transaction data without API key registration
Fit
Best for
- —Agents or apps needing x402-compatible pay-per-call receipt retrieval
- —Developers exploring x402 protocol integrations on Base
- —Use cases where keyless, instant API access is preferred
Not for
- —Bulk transaction history retrieval (this is a single-receipt endpoint)
- —Users who need detailed API documentation or OpenAPI specs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/179/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, but documentation is effectively nonexistent — all doc/pricing/API pages return only 'Connect wallet'. No OpenAPI spec, no response schema, no examples. The endpoint path suggests a single fixed resource (transaction 179) rather than a general-purpose API, and its actual utility is unclear.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) are all empty beyond 'Connect wallet' — no usable docs available.
- —This endpoint targets a specific transaction ID (179); it is unclear whether other transaction IDs are accessible or what the receipt contains.
- —No OpenAPI spec or response schema is provided; request/response formats are unknown.
- —The broader platform advertises many endpoints but none have documented schemas or examples.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/179/receipt
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/179/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limitshttps://lowpaymentfee.com
- —Documentation pages show only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs