x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 305) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of APIs spanning 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 $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, the specific endpoint being listed here is a transaction receipt resource under /api/v1/transactions/305/receipt, which does not appear in the site's publicly listed API catalog.
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 examples, and no detailed documentation for this or any other endpoint. The x402 challenge was successfully captured (HTTP 402), confirming the endpoint is live.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 305 via a single micropayment
- —Demonstrating x402 payment-gated API access on Base
- —Integrating pay-per-call receipt retrieval into an agent workflow
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to fetch transaction receipts without API key management
- —Micropayment-based API consumption with no subscription
Not for
- —Bulk retrieval of many different transaction receipts (only transaction 305 is exposed at this path)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Production workloads requiring SLA guarantees or support
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/305/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation, no OpenAPI schema, no request/response examples, and the specific endpoint (transaction 305 receipt) is not listed in the site's own API catalog. The docs, pricing, and README pages are all blank beyond a wallet-connect prompt.
Warnings
- —No OpenAPI spec or schema available for request or response bodies
- —The /docs, /pricing, /api, and /README pages contain no usable documentation
- —This specific endpoint (/api/v1/transactions/305/receipt) is not listed in the site's public API catalog — its purpose and response format are unknown
- —All other crawled pages beyond the homepage returned only 'Connect wallet' with no content
Citations
- —The x402 challenge returns HTTP 402 with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/305/receipt
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/305/receipt
- —All listed APIs are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com