Transaction receipt retrieval via x402 micropayment on Base network, $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (transaction ID 383) behind an x402 paywall. It is part of a broader platform offering numerous pay-per-call API endpoints across categories including data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/383/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header containing a signed payment of up to 20,000 base units of USDC (i.e., $0.02, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. No API keys or rate limits are advertised; access is gated purely by micropayment.
The platform's landing page lists 16 endpoints spanning metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation. Documentation pages beyond the landing page returned only a "Connect wallet" prompt with no further technical detail, so the exact request/response schemas for this receipt endpoint are unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 383 via programmatic micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Agent-driven receipt fetching without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need to fetch transaction receipts on-demand
- —Use cases requiring keyless, pay-as-you-go API access on Base
Not for
- —Bulk or high-volume receipt retrieval (no documented batch endpoint)
- —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/383/receipt \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-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 spec, no request/response schema documentation, no examples, and the docs/pricing/README pages all returned only a wallet-connect prompt. The specific purpose of this receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown.
- —Documentation pages (/docs, /pricing, /README, /api) returned only 'Connect wallet' with no technical content.
- —The endpoint is for a specific transaction ID (383); it is unclear whether this generalizes to other transaction IDs.
- —The broader platform lists many endpoints but none have documented schemas or examples.
Citations
- —The endpoint returns a 402 challenge requiring X-PAYMENT header with x402 version 1 on Base networkhttps://lowpaymentfee.com/api/v1/transactions/383/receipt
- —maxAmountRequired is 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02https://lowpaymentfee.com/api/v1/transactions/383/receipt
- —Platform advertises $0.02/request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —16 endpoints listed across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com