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 39) 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/39/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the accepted payment scheme (exact), the USDC asset contract on Base (`0x8335…`), and a maximum amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). No API keys or rate limits are advertised; access is granted purely through per-request micropayment.
The platform's landing page lists additional endpoints spanning sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. However, no OpenAPI schema, detailed documentation, or example request/response payloads were found during the crawl. The docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. Because of this, the actual data returned by this receipt endpoint and the broader platform's endpoints remains unclear.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 39 via a single micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that can settle USDC payments on Base for per-call access
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —High-volume batch retrieval where per-request fees add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/39/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid USDC payment proof to receive the receipt.Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no documentation, no example requests or responses, and the crawled docs/pricing/README pages are all empty beyond a wallet-connect prompt. The purpose of this specific receipt endpoint is opaque.
Warnings
- —No OpenAPI or schema documentation available for any endpoint on the platform
- —Docs, pricing, API, and README pages all render only 'Connect wallet' with no content
- —The specific data returned by /api/v1/transactions/39/receipt is unknown — it may be a demo or placeholder
- —The broader platform lists many endpoint categories but none could be verified beyond the landing page descriptions
Citations
- —Endpoint returns 402 with x402 challenge, maxAmountRequired 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/39/receipt
- —Platform advertises $0.02/request pricing 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/39/receipt
- —Docs, pricing, API, and README pages show only 'Connect wallet'https://lowpaymentfee.com/docs