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/315/receipt`) behind an x402 paywall. The provider operates a broad suite of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request and settled in USDC on the Base network. No API keys, rate limits, or upfront commitments are required — callers simply attach an x402 payment header to each request.
The specific endpoint probed here serves a transaction receipt for transaction ID 315. The x402 challenge confirms the endpoint is live, accepting POST requests, and requires a maximum payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The response MIME type is application/json.
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 request/response examples, and no description of what fields the receipt JSON contains. The provider's landing page lists many other endpoints across analytics, AI, finance, and utility categories, all at the same $0.02 price point, but none have documented schemas either.
Capabilities
Use cases
- —Retrieving a JSON receipt for a specific transaction via micropayment
- —Programmatic access to transaction data without API key registration
- —Agent-driven workflows that need proof-of-transaction receipts
Fit
Best for
- —Agents or scripts needing quick, keyless access to transaction receipts
- —Developers testing x402 payment flows on Base
- —Low-volume, pay-as-you-go transaction data retrieval
Not for
- —Bulk or high-volume transaction data exports (no batch endpoint documented)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/315/receipt \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no documented request parameters, no example responses, and the docs/pricing/README pages are all empty beyond a wallet-connect prompt. The specific purpose of this receipt endpoint (transaction 315) is opaque. Effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, and README pages render only 'Connect wallet'
- —No OpenAPI or JSON schema for request or response bodies
- —The endpoint is for a specific transaction ID (315); it is unclear whether other transaction IDs are supported or how to discover them
- —The broader provider lists many endpoints but none have documented schemas
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/315/receipt
- —All APIs priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/315/receipt
- —Docs, pricing, API, and README pages show only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs