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 182) behind an x402 paywall. It is part of a broader platform that offers 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/182/receipt` accepts POST requests and returns an `application/json` response. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The challenge advertises a `maxAmountRequired` of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout.
The platform markets itself as requiring no API keys, no rate limits, and no commitments — just per-request micropayments. Documentation pages (/docs, /pricing, /api) appear to require a wallet connection and contain no additional readable content. There is no OpenAPI spec, no detailed schema documentation, and no example request/response bodies available from the crawl. The actual data returned by this receipt endpoint is unknown beyond its JSON MIME type.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 182 via micropayment
- —Demonstrating x402 protocol integration for agent-to-API payments
- —Accessing pay-per-request infrastructure services without API key management
Fit
Best for
- —Developers exploring x402 protocol micropayments
- —Agents that need to purchase API access on-the-fly with USDC on Base
- —Projects requiring keyless, per-call API access
Not for
- —Bulk data retrieval where per-request fees add up quickly
- —Users without a Base-compatible wallet or USDC balance
- —Anyone needing detailed API documentation or OpenAPI specs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/182/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a landing page, no example request/response bodies, and the specific purpose of this receipt endpoint is opaque. The docs/pricing/api pages all render only a wallet-connect prompt with no useful content.
Warnings
- —No OpenAPI or schema documentation available
- —Documentation pages (/docs, /pricing, /api) return only a wallet-connect prompt with no readable content
- —The specific data returned by this receipt endpoint is unknown — only the MIME type (application/json) is confirmed
- —This appears to be a single transaction-specific receipt endpoint (transaction 182); unclear if it generalizes
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/182/receipt
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/182/receipt