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 362) 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.
The specific endpoint probed (/api/v1/transactions/362/receipt) returns a valid x402 challenge (HTTP 402) requesting payment of up to 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 x402 "exact" scheme to wallet 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. The response MIME type is 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 examples of what the receipt payload actually contains. The endpoint is live and the x402 challenge is well-formed, but without documentation it is difficult to know what data is returned or what input parameters (if any) the POST body accepts.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 362 via micropayment
- —Agent-driven pay-per-call data access without API key management
- —Programmatic access to receipts settled on Base L2 in USDC
Fit
Best for
- —Agents that need keyless, pay-per-call API access
- —Developers experimenting with x402 payment protocol on Base
- —Scenarios requiring no subscription or rate-limit constraints
Not for
- —Users needing detailed API documentation or schemas before integrating
- —Bulk or high-volume data retrieval where per-call pricing is inefficient
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/362/receipt
# Returns HTTP 402 with x402 challenge.
# Include X-PAYMENT header with signed USDC payment to complete the request.Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge with clear pricing. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples of the actual receipt payload. The endpoint path suggests a single fixed resource (transaction 362) rather than a general-purpose API, which limits utility.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no usable content.
- —No OpenAPI or schema documentation available — request body and response structure are unknown.
- —This endpoint targets a specific transaction ID (362); it is unclear whether it generalizes to other transaction IDs.
- —The platform advertises many API categories (AI, analytics, finance, utilities) but no evidence of documentation or working examples for any of them.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/362/receipt
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/362/receipt
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform advertises APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com