Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 358) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme. The cost per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call 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 listed at a uniform $0.02 per request. However, the specific endpoint being listed here is scoped to `/api/v1/transactions/358/receipt`, which appears to return a receipt for a particular transaction.
Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the receipt payload contains. The endpoint is confirmed live (returns a proper 402 challenge), but the actual response format and fields are unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 358 via a single micropayment
- —Demonstrating x402 pay-per-call integration on the Base network
- —Programmatic access to transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need keyless, pay-per-call API access on Base
- —Projects requiring USDC-settled micropayment workflows
Not for
- —Production use cases requiring documented response schemas and SLAs
- —Bulk or batch transaction receipt retrieval (single resource endpoint)
- —Users who need fiat or non-crypto payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/358/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and the endpoint is scoped to a single hardcoded transaction ID (358), making its general utility unclear.
Warnings
- —No OpenAPI or schema documentation available — response format is entirely unknown
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —Endpoint is scoped to a single transaction ID (358); unclear if this is a demo or production resource
- —No request body schema or response examples are provided anywhere
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/358/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com