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 284) 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 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network via the x402 protocol.
The specific endpoint probed (/api/v1/transactions/284/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the site's advertised pricing. Payment is made via the x402 "exact" scheme, requiring no API keys, no rate limits, and no upfront commitments — callers simply attach an X-PAYMENT header with a valid payment proof.
Documentation is extremely thin. The /docs, /pricing, /api, 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 examples of what the receipt payload actually contains. The endpoint accepts POST requests and returns application/json, but the structure of the response body is unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 284 via programmatic payment
- —Demonstrating x402 protocol integration for per-call USDC micropayments
- —Agent-driven access to paid data endpoints without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need keyless, pay-per-call API access settled in USDC
- —Prototyping micropayment-gated API workflows
Not for
- —Users needing detailed API documentation or response schemas before integrating
- —High-volume batch retrieval where per-call pricing may add up
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/284/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-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 spec, no documented request/response schema, no examples, and the docs pages are empty stubs. The specific purpose of this particular receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — response structure is entirely unknown
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
- —This endpoint is for a specific transaction ID (284); unclear if it generalizes or is a demo
- —The broader platform advertises many API categories but none have documented schemas
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/284/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/284/receipt
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com