Retrieve transaction receipt data via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt resource (specifically transaction ID 350) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics (metrics, reports, data export, insights), AI/ML (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 on the Base network. However, this specific listing covers only the `/api/v1/transactions/350/receipt` endpoint.
Documentation 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 schema, no example request/response payloads, and no description of what the receipt object contains. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the actual response schema and data semantics are unknown.
Capabilities
Use cases
- —Retrieving transaction receipt details for transaction 350 via programmatic micropayment
- —Demonstrating x402 protocol integration for pay-per-call API access
- —Building agent workflows that pay for data on-the-fly without API key management
Fit
Best for
- —Developers experimenting with x402 protocol payments on Base
- —Agents that need to fetch transaction receipts without pre-registration
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Bulk transaction receipt retrieval (only one transaction ID is exposed at this endpoint)
- —Users who need detailed API documentation or guaranteed SLAs
- —Production systems requiring well-documented response schemas
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/350/receipt \
-H "X-PAYMENT: <x402_payment_proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but documentation is essentially nonexistent — docs/pricing/API pages all show only 'Connect wallet'. There is no OpenAPI schema, no example responses, and the purpose of this specific receipt endpoint is unclear. The listing is effectively a stub.
Warnings
- —No documentation available — all doc pages render only 'Connect wallet'
- —No OpenAPI or output schema describing the receipt response format
- —This endpoint is scoped to a single transaction ID (350); unclear if other transaction IDs are supported at different paths
- —The platform lists many other endpoints but none have documented schemas or examples
Citations
- —Endpoint returns 402 with x402 challenge on POST, confirming it is livehttps://lowpaymentfee.com/api/v1/transactions/350/receipt
- —Payment is 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network, equaling $0.02https://lowpaymentfee.com/api/v1/transactions/350/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Basehttps://lowpaymentfee.com
- —Platform lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com