Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt for transaction ID 288 via the x402 payment protocol. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all settled on the Base network using USDC.
The specific endpoint `/api/v1/transactions/288/receipt` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per call (USDC uses 6 decimals). The platform's landing page confirms a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and no minimum commitments required.
The broader lowpaymentfee.com platform lists endpoints for metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. However, no OpenAPI schema, detailed documentation, or example request/response payloads were found during the crawl; the docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 288 via programmatic pay-per-call access
- —Integrating x402-compatible agents that settle payments in USDC on Base
- —Accessing low-cost API services without managing API keys or subscriptions
Fit
Best for
- —Agents or bots that support x402 payment protocol on Base
- —Developers wanting zero-commitment, pay-per-use API access
- —Use cases requiring USDC-settled micropayments per request
Not for
- —Users needing detailed API documentation or OpenAPI specs before integrating
- —Bulk or high-volume use cases where per-request pricing may add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/288/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment on Base to receive the receipt.Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI schema, no example request/response, and no meaningful documentation — the docs/pricing/README pages are all empty beyond a wallet-connect prompt. The specific purpose of a 'transaction 288 receipt' is unclear without further context.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —All documentation pages (docs, API, pricing, README) returned only a 'Connect wallet' prompt with no content
- —The endpoint is for a specific transaction ID (288); it is unclear whether this is a general-purpose receipt endpoint or a single fixed resource
- —No example request or response payloads are available to verify what the endpoint actually returns
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/288/receipt
- —The platform charges $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/288/receipt