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 229) 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 data (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 required.
The specific endpoint probed (/api/v1/transactions/229/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 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 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. The purpose and structure of the "transaction receipt" response body is unknown beyond the MIME type. The platform appears to be a demonstration or early-stage x402 API marketplace.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 229 via a single micropayment
- —Demonstrating x402 protocol payment flows for agent-to-API commerce
- —Exploring pay-per-request API access without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call API access on Base
- —Testing micropayment-gated endpoint integrations
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk data retrieval or high-volume analytics (no documented batch support)
- —Users who need fiat-only payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/229/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 request/response schema, no documentation beyond a wallet-connect prompt, and the specific purpose of this transaction receipt endpoint is unclear. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The specific endpoint is for a single transaction ID (229); unclear if this generalizes
- —Platform appears to be early-stage or a demo; reliability and longevity are uncertain
Citations
- —Platform advertises $0.02 per request pricing 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/229/receipt
- —Platform lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com