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 295) 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 via the x402 protocol.
The specific endpoint probed (/api/v1/transactions/295/receipt) returns a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this equates to $0.02 per call — consistent with the platform's advertised flat pricing. Payment is made via the x402 "exact" scheme to the specified payTo address. No API keys or rate limits are advertised; access is granted purely through on-chain micropayment.
Documentation is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what data is returned or what request body (if any) is expected.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 295 via micropayment
- —Programmatic access to pay-per-request APIs without API key management
- —Agent-driven data retrieval settled in USDC on Base
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need keyless, pay-per-call API access on Base
- —Use cases requiring on-chain payment settlement for API calls
Not for
- —Users needing detailed API documentation or response schemas before integrating
- —High-volume batch retrieval where per-call micropayments add friction
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/295/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment to proceed.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 documentation of request/response schemas, no examples, and the docs pages are empty. The specific endpoint appears to be a single transaction receipt rather than a general-purpose API, limiting its utility without further context.
Warnings
- —No OpenAPI or schema documentation available — response format is unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —This endpoint is for a specific transaction ID (295); it is unclear whether it generalizes to other transaction IDs
- —The platform advertises many API categories (AI, analytics, finance, utilities) but no evidence of actual functionality behind them was found
Citations
- —Platform advertises $0.02 per request flat pricing with no API keys, no rate limits, on Base networkhttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/transactions/295/receipt
- —Platform lists endpoints for analytics, AI/ML, finance, and infrastructure categorieshttps://lowpaymentfee.com