Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt retrieval service. The specific path `/api/v1/transactions/90/receipt` returns a receipt for transaction ID 90 in JSON format, payable per-call with USDC on the Base network. The x402 challenge confirms the endpoint is live and accepts exact-scheme payments.
The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payments settle in USDC on the Base L2 network.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available from the crawled material. The specific behavior and response format of the transaction receipt endpoint can only be inferred from the x402 challenge metadata (mimeType: application/json, method: POST). The platform appears to be a demonstration or early-stage deployment of x402 micropayment-gated APIs.
Capabilities
Use cases
- —Retrieving transaction receipts on a per-call payment basis
- —Programmatic access to transaction data without API key management
- —Agent-driven workflows that need verifiable transaction records with micropayment settlement
Fit
Best for
- —Developers experimenting with x402 pay-per-call patterns
- —Agents needing keyless, on-demand transaction receipt access
- —Projects already using USDC on Base for micropayments
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk transaction data retrieval (pay-per-call model may be inefficient at scale)
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/90/receipt
# Returns 402 with x402 payment challenge.
# Include X-PAYMENT header with a valid x402 payment token (USDC on Base) to receive the receipt.Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 per request in USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no usage examples, and all documentation pages render only a wallet-connect prompt. The actual response payload is unknown.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no technical content
- —No OpenAPI or schema definition found; request body and response format are undocumented
- —The endpoint path includes a hardcoded transaction ID (90), suggesting this may be a demo or single-resource endpoint rather than a general-purpose API
- —Platform appears to be early-stage or a proof-of-concept for x402 micropayments
Citations
- —Endpoint returns 402 with x402 challenge accepting USDC on Base network, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/transactions/90/receipt
- —All APIs priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/90/receipt