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-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/46/receipt` returns a JSON response (MIME type `application/json`) when a valid x402 payment header is supplied. The x402 challenge advertises a max amount of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the "exact" scheme with a 300-second timeout. No API keys or rate limits are advertised; access is purely payment-gated.
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 output schema stub, and no examples of what the receipt payload actually contains. The platform lists many other endpoints (analytics, AI, finance, utilities) at the same $0.02 price point, but none have documented schemas or sample payloads available from the crawl.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 46 via programmatic payment
- —Demonstrating x402 protocol integration for agent-to-agent micropayments
- —Accessing pay-per-use infrastructure without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing keyless, pay-per-call API access settled in USDC
- —Prototyping micropayment-gated service architectures
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based API access without crypto wallets
- —High-throughput use cases where per-request crypto settlement adds unacceptable latency
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/46/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"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 spec, no documented request body schema, no response schema, and no examples. The docs pages are empty beyond a wallet-connect prompt. The specific resource (transaction 46 receipt) is opaque — it's unclear what data it returns or what inputs it accepts. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for any endpoint on the platform
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
- —The endpoint path references a specific transaction ID (46), suggesting it may be a fixed demo resource rather than a general-purpose API
- —No request body schema or response payload examples are available from any source
- —The platform lists many endpoints (AI, analytics, finance, utilities) but none have verifiable functionality from the crawl
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/46/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/46/receipt
- —Payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/transactions/46/receipt