x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 365) 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/365/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 the specified payTo address, with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
Documentation is extremely sparse: the /docs, /pricing, /api, 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 usage examples available. The nature of the "receipt" data returned is not documented beyond the endpoint path and MIME type.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 365 via a single micropayment
- —Programmatic access to paid API resources without API key management
- —Agent-driven pay-per-call data retrieval on Base L2
Fit
Best for
- —Agents or scripts that need one-off paid data retrieval without subscription overhead
- —Developers exploring x402 payment protocol integrations
- —Use cases where no-signup, no-API-key access is preferred
Not for
- —Users needing detailed API documentation or response schema guarantees before integrating
- —High-volume batch retrieval where per-call pricing may add up
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/365/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment to receive the receipt.Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge with clear pricing. However, there is no OpenAPI spec, no documented request/response schema, no usage examples, and the docs pages are empty. The purpose of the 'transaction receipt' resource is unclear, making this effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet'
- —No OpenAPI or schema definition found for request or response payloads
- —The specific data returned by the transaction receipt endpoint is undocumented
- —The broader platform advertises many endpoints but none have documented schemas
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/365/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/365/receipt
- —Documentation pages (/docs, /pricing, /api, /README) render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs