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 65) 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/65/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers receive a 402 challenge with an `exact` payment scheme requiring up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) sent to the specified payTo address on Base. No API keys or rate limits are advertised; access is granted per-request upon payment. The payment timeout is 300 seconds.
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 documentation, and no usage examples available from the crawled material. The platform's landing page lists many endpoints across different domains (sentiment analysis, summarization, geocoding, gas estimates, etc.), but without documentation it is unclear what data or functionality this particular receipt endpoint returns beyond its generic "Premium API Access" label.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 65 via a micropayment-gated API
- —Demonstrating x402 protocol integration for per-call USDC payments on Base
- —Agent-driven programmatic access to paid data endpoints without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need keyless, pay-per-call API access settled in USDC
- —Testing micropayment flows for transaction data retrieval
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —High-volume batch retrieval where per-request fees add up quickly
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/65/receipt
# Returns 402 with x402 challenge. Include X-PAYMENT header with signed USDC payment on Base to access.Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the purpose of this specific receipt endpoint is unclear. The listing is effectively a stub.
Warnings
- —No OpenAPI or schema documentation available — endpoint behavior must be inferred from the generic description alone
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no technical content
- —The specific resource '/api/v1/transactions/65/receipt' is hardcoded to transaction ID 65; it is unclear if this is parameterizable or a fixed demo
- —The platform lists many diverse endpoints (AI, finance, geo, etc.) all at $0.02 — unclear whether these are fully implemented or placeholders
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/65/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 advertises categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com
- —Documentation pages render only a 'Connect wallet' prompt with no further contenthttps://lowpaymentfee.com/docs