x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 34) 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 priced at $0.02 per request, settled in USDC on the Base network, with no API keys, no rate limits, and no minimum commitments.
The specific endpoint probed — `/api/v1/transactions/34/receipt` — returns a valid x402 challenge (version 1, scheme "exact") requesting up to 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per call. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
Documentation is extremely sparse — the /docs, /pricing, /api, 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 platform's landing page lists many API paths but provides no detail on request parameters or response formats for any of them. Treat this listing as a stub until richer documentation becomes available.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 34 via a single micropayment
- —Demonstrating x402 protocol payment flows on Base with USDC
- —Integrating pay-per-request APIs without API key management
Fit
Best for
- —Agents or developers experimenting with x402 payment protocol
- —Use cases requiring keyless, pay-as-you-go API access on Base
- —Micropayment-gated data retrieval
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk or high-volume data retrieval where per-call pricing is inefficient
- —Users who need fiat-only payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/34/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-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 all documentation pages are empty stubs showing only 'Connect wallet'. The specific purpose of this receipt endpoint is unclear beyond its URL path.
Warnings
- —No OpenAPI or schema documentation available for any endpoint on the platform
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
- —The specific endpoint is for a hardcoded transaction ID (34); unclear if this is a demo or a real resource
- —No response schema or example payloads are documented anywhere
- —The platform lists many API paths on its landing page but none have documented inputs or outputs
Citations
- —The endpoint returns an x402 challenge requesting up to 20,000 base units of USDC on Base with a 300-second timeouthttps://lowpaymentfee.com/api/v1/transactions/34/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/34/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs