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 214) 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/214/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 translates to $0.02 per call, consistent with the site's advertised pricing. Payment is made via the "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are required — access is purely payment-gated.
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 examples of what the receipt payload actually contains. The platform lists many endpoints on its landing page, but this specific listing is for the transaction receipt endpoint only.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 214 via programmatic payment
- —Demonstrating x402 protocol payment flows on Base
- —Agent-driven pay-per-request data retrieval without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access on Base
- —Retrieving specific transaction receipts behind a micropaywall
Not for
- —Bulk or high-volume transaction receipt retrieval (no documented batch support)
- —Users who need detailed API documentation or response schema guarantees
- —Anyone needing receipts for transactions other than ID 214 (this endpoint is resource-specific)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/214/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. However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty stubs. The endpoint is for a single hardcoded transaction ID with no explanation of what the receipt contains.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
- —No OpenAPI or schema definition found for request or response payloads
- —This endpoint is for a specific transaction ID (214); it is unclear if other transaction IDs are available or how to discover them
- —The platform lists many other endpoints on its landing page but none have documented schemas
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/214/receipt
- —Payment address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with 300-second timeouthttps://lowpaymentfee.com/api/v1/transactions/214/receipt
- —Platform advertises APIs for analytics, AI/ML, finance/Web3, and infrastructure utilitieshttps://lowpaymentfee.com