x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 240) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI/ML inference (sentiment analysis, 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, settled in USDC on the Base network via the x402 protocol.
The specific endpoint probed (/api/v1/transactions/240/receipt) returns a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this equals $0.02 per call, consistent with the site's advertised pricing. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. No API keys or rate limits are advertised; access is gated purely by micropayment.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what data is returned or what input parameters are expected beyond a POST request.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction ID 240 via a single micropayment
- —Programmatic access to paid API endpoints without API key management
- —Agent-driven workflows that settle per-call costs in USDC on Base
Fit
Best for
- —Developers exploring x402 micropayment-gated APIs
- —Agents that can settle USDC payments on Base L2
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Users needing detailed API documentation or response schemas before integrating
- —High-volume batch processing where per-call micropayments add friction
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/240/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment on Base to access.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 spec, no documentation beyond a landing page listing, no request/response schema, and no examples of what the receipt payload contains. The docs pages are empty. This is effectively a stub listing.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
- —No OpenAPI or schema definition; request parameters and response format are unknown
- —The endpoint path references a specific transaction ID (240); it is unclear whether this is a general-purpose endpoint or a single fixed resource
- —The broader platform lists many API categories (AI, analytics, finance, utilities) but none have documented schemas or examples
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/240/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/240/receipt
- —All endpoints are listed at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform advertises APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com