x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 186) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (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 commitments required.
The specific endpoint probed (/api/v1/transactions/186/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the platform's advertised pricing. Payment is made via the x402 "exact" scheme to the specified payTo address. The endpoint accepts POST requests and returns application/json.
Documentation on the site is extremely thin — 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. The nature of what the "transaction receipt" contains is not documented, making it difficult to assess the endpoint's utility without actually paying for a call.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 186 via a micropayment
- —Demonstrating x402 protocol payment flows on Base
- —Agent-driven pay-per-call data retrieval without API keys
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base L2
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Users needing detailed API documentation or schemas before purchasing
- —High-volume batch retrieval where per-call costs add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/186/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 documentation, no OpenAPI spec, no request/response schema, and no examples. The purpose of the specific 'transaction 186 receipt' is unexplained. The broader platform lists many endpoints but provides zero documentation for any of them.
Warnings
- —No API documentation available — /docs, /api, /pricing, /README all render only 'Connect wallet'
- —No OpenAPI or schema definition for request or response payloads
- —The specific resource (transaction 186 receipt) is unexplained — unclear what data is returned
- —The broader platform lists many endpoints but none have documented schemas or examples
- —Cannot verify actual functionality without paying for a call
Citations
- —Platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/transactions/186/receipt
- —Platform lists endpoints for analytics, AI/ML, finance/Web3, and infrastructure utilitieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no contenthttps://lowpaymentfee.com/docs