Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" receipt for transaction ID 394. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/394/receipt` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring a maximum of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals → $0.02) per call. Payment is made via the x402 exact scheme with no API keys, no rate limits, and no upfront commitments — the caller simply attaches an X-PAYMENT header with a valid payment proof.
Documentation on the site is extremely sparse: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema beyond the x402 outputSchema stub, and no examples of what the receipt payload actually contains. The platform lists many other endpoints (sentiment analysis, text summarization, embeddings, geocoding, etc.) at the same $0.02 price point, but none have documented schemas either.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 394 via a single paid API call
- —Demonstrating x402 pay-per-request flows on the Base network
- —Integrating USDC micropayments into agent workflows without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing keyless, pay-as-you-go API access
- —Projects requiring USDC-settled micropayment endpoints
Not for
- —Production workloads requiring well-documented request/response schemas
- —Users who need free or subscription-based API access
- —Applications requiring high-throughput batch processing with guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/394/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming pricing and network. However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty stubs. The specific purpose of this receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The endpoint is for a specific transaction ID (394); it is unclear whether this is a generic pattern or a fixed resource
- —The broader platform lists many endpoints but none have documented schemas or examples
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/394/receipt
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/394/receipt
- —All APIs 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 & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages render only a 'Connect wallet' prompt with no additional contenthttps://lowpaymentfee.com/docs