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 32) 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 pay-per-request APIs spanning data & analytics (metrics, reports, data export, insights), AI & ML (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 commitments required — just an x402 payment header.
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 schema documentation, and no usage examples available from the crawled material. The specific endpoint path (`/api/v1/transactions/32/receipt`) is not listed on the homepage's API catalog, making its exact purpose unclear beyond the generic "Premium API Access" description provided in the x402 challenge.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 32 via a single paid API call
- —Demonstrating x402 payment protocol integration for agent-to-agent commerce
- —Programmatic access to financial transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access to transaction receipts on Base
- —Projects that want keyless, wallet-authenticated API access
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —Bulk or high-volume transaction data retrieval (no documented batch support)
- —Users without a Base-compatible wallet or USDC balance
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/32/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (returns a valid 402 challenge with clear pricing), but documentation is essentially nonexistent — docs/pricing/README pages all show only 'Connect wallet'. No OpenAPI spec, no request/response schemas, no examples. The specific endpoint path is not even listed in the site's own API catalog. This is effectively a stub listing.
Warnings
- —No OpenAPI spec or schema documentation available
- —Docs, pricing, and README pages contain no usable content beyond 'Connect wallet'
- —The specific endpoint /api/v1/transactions/32/receipt is not listed in the site's own API catalog — purpose is unclear
- —No request body schema or response schema documented anywhere
- —Cannot verify what data the receipt endpoint actually returns
Citations
- —The endpoint returns a 402 challenge requiring USDC payment on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/transactions/32/receipt
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/32/receipt
- —All listed APIs are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs