x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 346) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (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 commitments — just an x402 payment header per call.
However, the specific endpoint being listed here (/api/v1/transactions/346/receipt) is not among the documented API categories on the landing page. It appears to be a transaction receipt retrieval endpoint, possibly returning details about a specific transaction. Documentation beyond the landing page is effectively empty (all sub-pages just show "Connect wallet"), so the exact request body format and response schema are unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID via micropayment
- —Programmatic access to transaction data without API key registration
- —Agent-driven workflows that need on-demand transaction verification
Fit
Best for
- —Agents or services that need to fetch transaction receipts on demand
- —Developers wanting key-free, pay-per-use API access on Base
- —Automated pipelines that can settle USDC payments via x402
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need detailed API documentation or OpenAPI specs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/346/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documentation for this specific endpoint, no example request/response, and all doc pages are empty. The endpoint path (/transactions/346/receipt) is not listed among the platform's advertised APIs, making its purpose uncertain.
Warnings
- —No documentation available — all doc/pricing/API pages return only 'Connect wallet' with no content.
- —The specific endpoint /api/v1/transactions/346/receipt is not listed among the platform's advertised API categories.
- —No request body schema or response schema is documented; integration requires trial and error.
- —Unknown whether this endpoint returns meaningful data or is a demo/placeholder.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/346/receipt
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/346/receipt
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Platform lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com