Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt retrieval API behind an x402 paywall. The specific resource `/api/v1/transactions/25/receipt` accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum amount of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). No API keys or rate limits are required — access is gated purely by the x402 micropayment protocol.
The provider, lowpaymentfee.com, hosts a broader suite of APIs across several categories: data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with the same x402 payment model on Base.
Documentation 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 schema, no request/response examples, and no description of what the transaction receipt endpoint actually returns. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what data to send or expect back.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call USDC micropayments
- —Integrating pay-per-use receipt lookups into agent workflows without API key management
- —Accessing financial transaction data via x402-gated endpoints on Base
Fit
Best for
- —Agents or services that need on-demand transaction receipt data with no subscription commitment
- —Developers experimenting with x402 micropayment-gated APIs
- —Workflows requiring keyless, pay-as-you-go API access on Base
Not for
- —Users needing detailed API documentation or request/response schemas before integration
- —High-volume batch processing where per-call pricing may add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/25/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and all documentation pages return only 'Connect wallet' with no usable content. The specific purpose of this particular receipt endpoint is undocumented.
Warnings
- —No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema provided for request or response bodies
- —The specific endpoint path (/api/v1/transactions/25/receipt) suggests a hardcoded transaction ID (25), which may indicate a demo or test resource rather than a general-purpose API
- —Purpose and data returned by this endpoint are entirely undocumented
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/25/receipt
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/25/receipt
- —All listed APIs are priced at $0.02 per request with no API keys, no rate limitshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/25/receipt
- —Documentation pages render only 'Connect wallet' with no technical contenthttps://lowpaymentfee.com/docs