Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/317/receipt`. It is part of a broader platform that offers dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all settled on the Base network using USDC via the x402 protocol.
The specific endpoint probed returns a receipt for transaction 317. The x402 challenge confirms it is live, accepting POST requests, and charges a maximum of 20,000 base units of USDC (0.02 USD) per call. The platform advertises uniform $0.02/request pricing across all endpoints, with no API keys, no rate limits, and no minimum commitments required. Payment is made inline via the X-PAYMENT header using the x402 exact scheme.
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. However, documentation pages (docs, pricing, README) returned only a "Connect wallet" prompt with no substantive content, so the actual behavior and response schemas of these endpoints remain undocumented.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction via a micropayment-gated endpoint
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Accessing financial or transactional data without API key registration
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need on-demand transaction receipts without subscription overhead
- —Projects already operating on the Base L2 network with USDC
Not for
- —Users who need detailed API documentation or response schema guarantees before integrating
- —High-volume batch retrieval where per-call pricing may add up
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/317/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no response schema, no example responses, and the docs/pricing/README pages are all empty stubs. The specific purpose of 'transaction 317 receipt' is opaque without further context.
Warnings
- —Documentation pages (/docs, /pricing, /README) return no useful content — only a 'Connect wallet' prompt.
- —No response schema or example response is available for this endpoint.
- —The endpoint path references a specific transaction ID (317); it is unclear whether this is a generic pattern or a single fixed resource.
- —The broader platform lists many endpoints but none have documented schemas or example payloads.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Base network.https://lowpaymentfee.com/api/v1/transactions/317/receipt
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/transactions/317/receipt