x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/332/receipt` returns a JSON response (MIME type `application/json`) when a valid x402 payment header is supplied. The x402 challenge advertises a `maxAmountRequired` of 20000 base units of USDC (contract `0x8335…2913` on Base), which equals $0.02 given USDC's 6 decimals. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the "exact" scheme with a 300-second timeout.
The platform advertises no API keys, no rate limits, and instant access. Documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all resolve but appear to require a wallet connection to render content, so detailed API schemas and response formats are not available from the crawl. The landing page lists 16 endpoints across four categories but provides no request/response examples or OpenAPI spec.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 332 via a single micropayment
- —Programmatic access to receipts without API key management
- —Agent-driven workflows that need verifiable transaction data on demand
Fit
Best for
- —Agents or services that need on-demand transaction receipts without subscription commitments
- —Developers experimenting with x402 payment-gated APIs on Base
- —Low-volume, pay-as-you-go access to financial transaction data
Not for
- —High-volume bulk receipt retrieval where per-call pricing adds up
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/332/receipt
# Returns 402 with x402 challenge. Supply X-PAYMENT header with valid USDC payment on Base to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI spec, no request/response schema, no documentation content (all doc pages require wallet connection), and the specific purpose of this receipt endpoint (transaction 332) is unclear. Effectively a stub listing.
Warnings
- —All documentation pages (/docs, /pricing, /api, /README) require wallet connection and returned no useful content during crawl.
- —No OpenAPI or JSON schema available — request body format and response structure are unknown.
- —The endpoint references a specific transaction ID (332); it is unclear whether this is a demo resource or a real transaction receipt.
- —The platform lists many endpoints but none have published schemas or example payloads.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base with a 300-second timeout.https://lowpaymentfee.com/api/v1/transactions/332/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/transactions/332/receipt