Transaction receipt retrieval via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource path `/api/v1/transactions/389/receipt`) behind an x402 paywall. Payment is settled in USDC on the Base network at $0.02 per request (20,000 base units with 6 decimals). The endpoint accepts POST requests and returns JSON.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto market data, and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments — payment is handled entirely through the x402 protocol using USDC 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 spec, no request/response schema documentation, and no usage examples available from the crawled content. The specific endpoint probed here (`/transactions/389/receipt`) appears to be a single-resource receipt lookup, but the exact request body format and response structure are unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt by ID via programmatic micropayment
- —Integrating pay-per-call receipt lookups into agent workflows
- —Accessing financial transaction data without API key registration
Fit
Best for
- —Agents that can settle x402 payments in USDC on Base
- —Developers wanting zero-signup, pay-per-use transaction data
- —Workflows requiring on-demand receipt retrieval without rate limits
Not for
- —Users needing detailed API documentation or OpenAPI specs before integration
- —High-volume batch retrieval where per-request pricing adds up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/389/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, documentation is effectively nonexistent — all doc/pricing/API pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The specific purpose of this particular receipt endpoint (transaction 389) is unclear and may be a demo resource rather than a general-purpose API.
Warnings
- —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content.
- —No OpenAPI spec or request/response schema available — request body format and response structure are unknown.
- —The endpoint path references a specific transaction ID (389), which may be a fixed demo resource rather than a parameterized endpoint.
- —The platform lists many API categories (AI, analytics, finance, utilities) all at $0.02, but no evidence of actual functionality behind any of them was found in the crawl.
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/389/receipt
- —maxAmountRequired is 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02https://lowpaymentfee.com/api/v1/transactions/389/receipt
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages show only 'Connect wallet' with no documentation contenthttps://lowpaymentfee.com/docs