Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt retrieval service. The specific endpoint `/api/v1/transactions/99/receipt` accepts POST requests and returns JSON responses, gated behind an x402 payment challenge. Payment is settled in USDC on the Base network at a cost of $0.02 per request (20,000 base units with 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning 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 a uniform $0.02 per request with no API keys, no rate limits, and no minimum commitments required.
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 or what input it expects beyond a POST method. The endpoint is confirmed live (returns a valid x402 402 challenge), but the lack of documentation makes it difficult to assess the actual utility or data quality of the service.
Capabilities
Use cases
- —Retrieving transaction receipts via a pay-per-call model
- —Programmatic access to receipt data without API key management
- —Agent-driven payment flows using x402 on Base
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents that need keyless, pay-as-you-go API access
- —Use cases requiring USDC-settled micropayments on Base
Not for
- —Production workloads requiring well-documented APIs with schemas and examples
- —Users who need free or subscription-based access without per-call crypto payments
- —Anyone needing detailed transaction receipt specifications before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/99/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid payment to access.Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and the purpose of the specific '/transactions/99/receipt' endpoint is unclear. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —The endpoint path includes a hardcoded ID '99' — unclear if this is parameterized or a single fixed resource
- —No examples of successful responses are available anywhere in the crawled material
- —The breadth of advertised APIs (AI, finance, analytics, infrastructure) with zero documentation raises concerns about actual service maturity
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/99/receipt
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/99/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages show only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs