x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 228) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/228/receipt` accepts POST requests and returns an `application/json` response. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The maximum amount required is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. No API keys, rate limits, or subscriptions are required — access is purely pay-per-use.
The platform advertises additional endpoints for sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, and more, all at the same $0.02 price point. However, documentation beyond the landing page 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 example payloads available. The actual data returned by this receipt endpoint is unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 228 via a single micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Programmatic access to transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need one-off transaction receipt lookups
- —Use cases requiring keyless, pay-as-you-go API access on Base
Not for
- —Bulk or high-volume transaction data retrieval (no documented batch support)
- —Users who need detailed API documentation or request/response schemas before integrating
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/228/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no OpenAPI spec, no documented request or response schema, no example payloads, and the docs/pricing/README pages are all empty beyond a wallet connect prompt. The purpose of this specific receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are completely unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The endpoint is for a specific transaction ID (228); it is unclear whether other transaction IDs are available or what data the receipt contains
- —The broader platform advertises many endpoints but none have documented schemas
Citations
- —The endpoint returns a 402 challenge requiring 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/228/receipt
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform offers endpoints across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com