Transaction receipt retrieval via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (transaction ID 386) behind an x402 paywall. It is part of a broader platform offering a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/386/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers receive a 402 challenge containing payment details (asset, amount, payTo address), construct a signed USDC payment, and include it in the `X-PAYMENT` header on retry. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. No API keys, rate limits, or upfront commitments are required — access is instant once payment is included.
The platform advertises additional endpoints for metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. Documentation pages beyond the landing page were largely empty (showing only a "Connect wallet" prompt), so details on request/response schemas for this specific receipt endpoint are not available.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 386 via programmatic micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Agents autonomously purchasing transaction data without API key provisioning
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —AI agents that need to autonomously purchase API access on Base
- —Users who want pay-per-use access without subscriptions or API keys
Not for
- —Bulk retrieval of many transaction receipts (each call costs $0.02 individually)
- —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/386/receipt
# Returns 402 with x402 challenge. Parse the challenge, sign a USDC payment
# for 20000 base units ($0.02) to 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3,
# then retry with the X-PAYMENT header.Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge), but there is no OpenAPI schema, no documentation beyond a landing page, no example request/response bodies, and the endpoint path suggests a single hardcoded resource (transaction 386) rather than a parameterized API. Docs pages all returned only 'Connect wallet' with no content.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —Documentation pages (/docs, /api, /pricing, /README) are effectively empty, showing only a wallet-connect prompt
- —The endpoint path references a specific transaction ID (386); it is unclear whether this is parameterized or a single fixed resource
- —The platform lists many endpoints on its landing page but none have documented schemas or examples
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/386/receipt
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform offers endpoints across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com