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 261) 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/261/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 site's advertised pricing. Payment is made via the x402 "exact" scheme to wallet 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. No API keys or rate limits are advertised; access is instant upon payment.
Documentation 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 schema, no request/response examples, and no detailed documentation for any endpoint. The platform's actual data sources and model providers are unknown. The transaction receipt endpoint's purpose and response format are not documented beyond the generic "Premium API Access" label.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 261 via micropayment
- —Programmatic access to pay-per-request data endpoints without API key management
- —Agent-driven API consumption settled in USDC on Base
Fit
Best for
- —Developers wanting keyless, pay-per-call API access
- —AI agents that can settle x402 payments in USDC on Base
- —Quick one-off data retrieval without subscription commitments
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —High-volume consumers who need bulk pricing or rate-limit guarantees
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/261/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment to complete request.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 schema, no request/response examples, and the specific endpoint's purpose (transaction 261 receipt) is opaque. The broader platform lists many endpoints but provides zero detail on any of them.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content.
- —No OpenAPI or JSON schema describing request parameters or response format.
- —The specific endpoint (/api/v1/transactions/261/receipt) references a hardcoded transaction ID; unclear what data it returns or how it generalizes.
- —The platform advertises many endpoint categories (AI, finance, analytics, infrastructure) but provides no evidence of actual underlying data sources or models.
Citations
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network.https://lowpaymentfee.com/api/v1/transactions/261/receipt
- —Platform lists endpoints for analytics, AI/ML, finance/Web3, and infrastructure utilities.https://lowpaymentfee.com