x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 38) behind an x402 paywall. It is part of a broader platform that advertises multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/38/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 exact-payment scheme: the caller must attach an X-PAYMENT header containing a signed USDC payment of up to 0.02 USDC (maxAmountRequired=20000 base units, USDC has 6 decimals) to the specified payTo address on Base. No API keys or rate limits are advertised; access is purely pay-per-call.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no explanation of what the receipt payload actually contains. The platform appears to be a demonstration or early-stage x402 showcase rather than a mature production API.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 38 via a micropayment
- —Demonstrating x402 protocol payment flows on Base
- —Testing agent-driven pay-per-call API consumption
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can sign USDC payments on Base
- —Testing micropayment-gated API access patterns
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or API-key-based authentication
- —Bulk data retrieval or high-throughput analytics
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/38/receipt \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no documented request body or response schema, and all documentation pages are empty beyond a wallet-connect prompt. The specific resource (transaction 38 receipt) is unexplained. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown.
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content.
- —The endpoint targets a specific transaction ID (38); it is unclear whether this is a generic pattern or a fixed resource.
- —Platform appears to be a demo or early-stage project; production readiness is uncertain.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired=20000 in USDC (asset 0x8335…) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/38/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 Data & Analytics, AI & ML, Finance & Web3, and Infrastructure API categorieshttps://lowpaymentfee.com