x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 382) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network, with no API keys, no rate limits, and no commitments required.
This particular endpoint (/api/v1/transactions/382/receipt) returned a live x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the platform's advertised pricing. The payment scheme is "exact" with a 300-second timeout, and the endpoint accepts POST requests returning application/json.
Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the receipt payload actually contains. The endpoint appears live and functional based on the 402 challenge, but the lack of documentation makes it difficult to know what data is returned or what input parameters (if any) are expected in the POST body.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction 382 via a single micropayment
- —Demonstrating x402 protocol payment flows for agent-to-agent commerce
- —Integrating pay-per-request APIs without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand transaction receipt data without subscription overhead
- —Projects requiring USDC-settled micropayment API access on Base
Not for
- —Production workloads requiring detailed API documentation and SLAs
- —Bulk retrieval of many different transaction receipts (only transaction 382 is exposed at this URL)
- —Users who need fiat-only payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/382/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), but there is no OpenAPI schema, no documentation beyond a landing page listing, no request/response examples, and the specific purpose of this receipt endpoint is unexplained. The docs/pricing/API pages are all empty wallet-connect stubs.
Warnings
- —No API documentation available — docs, pricing, and API pages all show only 'Connect wallet' with no content.
- —No OpenAPI or schema definition for request or response payloads.
- —This URL is scoped to a single transaction ID (382); unclear if other transaction IDs are available or what the receipt contains.
- —The broader platform lists many endpoints (AI, finance, utils) but none have documented schemas or examples.
Citations
- —Platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The x402 challenge shows maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02.https://lowpaymentfee.com/api/v1/transactions/382/receipt
- —Platform lists endpoints for analytics, AI/ML, finance/Web3, and infrastructure utilities.https://lowpaymentfee.com