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 267) behind an x402 paywall. It is part of a broader platform offering a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per call and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/267/receipt` accepts POST requests and returns JSON. 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. No API keys or rate limits are advertised; access is entirely gated by micropayment.
Documentation on the site 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 documentation, and no usage examples. The platform lists many other endpoints (analytics, AI, finance, utilities) at the same $0.02 price point, but details on what data each returns are not available from the crawled material.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 267 via micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agent-driven data retrieval without API key management
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need keyless, pay-per-call API access on Base
- —Low-volume consumers who prefer micropayments over subscriptions
Not for
- —Users needing detailed API documentation or schemas before integrating
- —High-volume batch retrieval where per-request fees add up
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/267/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid payment proof to access.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. 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.
- —Docs, pricing, API, and README pages all render only 'Connect wallet' with no usable content.
- —The specific data returned by this transaction receipt endpoint is undocumented.
- —The 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 Base networkhttps://lowpaymentfee.com/api/v1/transactions/267/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/267/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