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 293) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme. The advertised cost is 20,000 base units of USDC, which equals $0.02 per request (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 across four categories: Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text 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 the same $0.02/request price point.
However, the specific endpoint being listed here — `/api/v1/transactions/293/receipt` — is not among the APIs advertised on the landing page. Its description is simply "Premium API Access" with no further documentation on request format, expected input fields, or response schema. The docs, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. Without documentation or example responses, the actual functionality of this particular endpoint remains unclear.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 293 via a single paid API call
- —Demonstrating x402 pay-per-call integration on the Base network
- —Agent-driven micropayment workflows that settle in USDC without API keys
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents needing keyless, pay-per-call API access on Base
- —Use cases requiring USDC-settled micropayments per request
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk or high-volume data retrieval (no batch pricing or documentation available)
- —Users who need fiat payment rails or non-crypto settlement
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/293/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge) and pricing is clear ($0.02 USDC on Base). However, the specific endpoint path (/api/v1/transactions/293/receipt) is not documented on the site, there is no OpenAPI schema, no request/response examples, and all documentation pages return only a wallet-connect prompt. The listing is effectively a stub with confirmed liveness.
Warnings
- —The endpoint /api/v1/transactions/293/receipt is not listed among the advertised APIs on the landing page — its purpose is unclear.
- —No documentation, request schema, or response schema is available; docs/pricing/README pages all return only 'Connect wallet'.
- —The endpoint path contains a hardcoded transaction ID (293), suggesting it may be a single-resource endpoint rather than a general-purpose API.
- —No robots.txt or agents.txt found; no OpenAPI spec available.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 in USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/293/receipt
- —All listed APIs are priced at $0.02/request with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —The platform advertises APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Docs, pricing, and README pages return only a 'Connect wallet' prompt with no substantive documentationhttps://lowpaymentfee.com/docs