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 (transaction ID 338) behind an x402 paywall. It is part of a broader platform that advertises multiple API categories — data & analytics, AI & machine learning, 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/338/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the accepted payment scheme (exact), the USDC asset contract on Base (`0x8335…`), and a maximum amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). No API keys are required; access is granted per-request upon valid payment. The platform advertises no rate limits and instant access.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's `outputSchema`, and no examples of what the receipt payload actually contains. The platform lists many other endpoints across analytics, AI, finance, and utility categories, but this listing covers only the `/api/v1/transactions/338/receipt` resource.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction (ID 338) via programmatic payment
- —Demonstrating x402 protocol integration for per-request micropayments
- —Agents that need to fetch financial transaction records without pre-registered API keys
Fit
Best for
- —Developers experimenting with x402 payment flows on Base
- —Agents needing keyless, pay-per-call access to transaction data
- —Micropayment-based API consumption without subscriptions
Not for
- —Bulk retrieval of many transaction receipts (only one transaction ID exposed)
- —Users who need detailed API documentation or response schemas before integrating
- —Production workloads requiring SLA guarantees or documented error handling
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/338/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid USDC payment to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what the receipt payload contains. The endpoint path is specific to a single transaction ID (338), making its general utility unclear.
Warnings
- —Documentation pages (/docs, /pricing, /api, /README) all render only 'Connect wallet' with no usable content.
- —No OpenAPI or schema describing the receipt response body — callers cannot know what they will receive before paying.
- —Endpoint is scoped to a single transaction ID (338); unclear if other transaction IDs are available or how to discover them.
- —The platform lists many other endpoints (AI, analytics, finance, utils) but none were probed; their availability is unverified.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02).https://lowpaymentfee.com/api/v1/transactions/338/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 USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/transactions/338/receipt