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 `/api/v1/transactions/359/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 receipt for transaction ID 359. It accepts POST requests and returns `application/json`. The x402 challenge confirms the endpoint is live, requesting a maximum of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, with a 300-second payment timeout.
Documentation beyond the landing page is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples. The broader platform advertises many endpoints (sentiment analysis, summarization, embeddings, price feeds, geocoding, etc.) but none have documented schemas. Treat this listing as a stub until richer documentation becomes available.
Capabilities
Use cases
- —Retrieving a structured receipt for a specific transaction via micropayment
- —Demonstrating x402 payment flow integration on Base network
- —Programmatic access to transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents that need on-demand transaction receipts without subscription overhead
- —Low-volume, pay-as-you-go API consumption on Base
Not for
- —High-volume batch receipt retrieval (no documented bulk endpoints)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/359/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation for request/response schemas, no OpenAPI spec, and all doc pages render only a wallet-connect prompt. The specific endpoint (transaction 359 receipt) is narrow and unexplained. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown.
- —All documentation pages (docs, API, pricing, README) return only a 'Connect wallet' prompt with no content.
- —This endpoint is for a single hardcoded transaction ID (359); it is unclear whether other transaction IDs are supported or how to discover them.
- —The broader platform advertises many endpoints but none have verifiable documentation or schemas.
Citations
- —The endpoint returns a 402 challenge requesting 20,000 base units of USDC on Base with a 300-second timeout.https://lowpaymentfee.com/api/v1/transactions/359/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/transactions/359/receipt
- —Documentation, API, pricing, and README pages render only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs