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 367) 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/367/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 equals $0.02 per call — consistent with the site's advertised pricing. Payment is made via the x402 "exact" scheme, with a 300-second timeout. No API keys or rate limits are required; access is granted purely through on-chain payment.
Documentation is extremely sparse. 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 and responding with a proper 402 challenge, but the lack of documentation makes it difficult to know what data is returned or what input parameters (if any) the POST body expects.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction 367 via a single paid API call
- —Programmatic access to receipt information without traditional API key management
- —Agent-driven workflows that need to fetch financial transaction records on-demand
Fit
Best for
- —Developers experimenting with x402 payment protocol integrations
- —Agents that can settle USDC payments on Base for per-call API access
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk retrieval of many transaction receipts (only one transaction ID is exposed at this endpoint)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/367/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-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 documented request/response schema, no examples, and the docs pages are empty. The endpoint path is specific to a single transaction ID (367), making its general utility unclear. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown
- —All documentation pages (/docs, /api, /pricing, /README) return only a 'Connect wallet' prompt with no content
- —Endpoint is scoped to a single transaction ID (367); unclear if other transaction IDs are available or how to discover them
- —The broader platform advertises many API categories (AI, analytics, finance, utilities) but none could be verified beyond the landing page listing
Citations
- —All endpoints priced at $0.02 per request 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/367/receipt
- —Platform advertises APIs for analytics, AI/ML, finance/Web3, and infrastructure utilitieshttps://lowpaymentfee.com