Pay-per-call transaction receipt endpoint on Base via x402, settling 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 231) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call 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 the same $0.02/request price point with no API keys, no rate limits, and no minimum commitments.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The specific endpoint probed (/api/v1/transactions/231/receipt) is not listed on the homepage's API catalog, so its exact purpose and response format are unclear beyond the generic "Premium API Access" description. The endpoint is confirmed live (returns a valid x402 402 challenge).
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 231 via a single micropayment
- —Agent-driven pay-per-call access without API key management
- —Programmatic access to paid resources settled on Base L2 in USDC
Fit
Best for
- —Developers experimenting with x402 payment protocol integrations
- —AI agents that need keyless, pay-per-call API access
- —Users who want to avoid subscription commitments for occasional API calls
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need bulk or discounted pricing for high-volume usage
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/231/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty. The specific endpoint path (transactions/231/receipt) is not listed in the site's own API catalog, making its purpose unclear.
Warnings
- —No OpenAPI or schema documentation available — all docs pages render only 'Connect wallet'
- —This specific endpoint (/api/v1/transactions/231/receipt) is not listed in the site's published API catalog
- —No request body schema or response schema documented anywhere
- —The endpoint appears to be for a single hardcoded transaction ID (231); unclear if this generalizes
Citations
- —The endpoint returns a valid x402 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/231/receipt
- —All listed APIs are priced at $0.02/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 (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs