Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/218/receipt`. 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 utility services — all gated via the x402 payment protocol on the Base network.
The specific endpoint probed returns a 402 challenge requesting payment in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base). The `maxAmountRequired` is 20,000 base units, which at 6 decimals for USDC equals $0.02 per request. Payment is made via the x402 `exact` scheme with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`.
The platform advertises a uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments required. Documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all resolve but appear to require a wallet connection to view content, so detailed API schemas and response formats are not available from the crawl. The exact data returned by the `/transactions/218/receipt` endpoint is unclear — it likely returns a receipt or confirmation object for a specific transaction, but no response schema or example is documented in the available material.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 218 via a micropayment
- —Programmatic access to paid API resources without API key management
- —Agent-driven workflows that need to fetch financial transaction data on-demand
Fit
Best for
- —Agents or scripts that can settle x402 payments in USDC on Base
- —Use cases requiring keyless, pay-per-call API access
- —Developers exploring x402 protocol integrations
Not for
- —Users who need detailed API documentation or response schemas before committing
- —High-volume batch retrieval where per-request fees add up quickly
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/218/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment on Base to access.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no response examples, and all documentation pages require wallet connection and returned no useful content. The specific purpose of this particular endpoint (transaction 218 receipt) is unclear and appears to be a single hardcoded resource rather than a parameterized API.
Warnings
- —Documentation pages (/docs, /pricing, /api, /README) all require wallet connection and returned no usable content during crawl.
- —The endpoint path includes a hardcoded transaction ID (218), suggesting this may be a single-resource endpoint rather than a general-purpose API.
- —No response schema or example response is available — the actual data returned is unknown.
- —The platform lists many endpoints (AI, finance, utils) but none have documented schemas; quality of underlying services is unverifiable.
Citations
- —The x402 challenge requests 20,000 base units of USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/transactions/218/receipt
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The endpoint accepts POST requests and returns application/json.https://lowpaymentfee.com/api/v1/transactions/218/receipt