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 behind an x402 paywall. The specific path `/api/v1/transactions/158/receipt` returns a receipt for transaction 158 in JSON format, payable via 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, settled in USDC on Base, with no API keys, no rate limits, and no minimum commitments required.
However, the specific endpoint being listed here — the transaction receipt — has a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02. Documentation beyond the landing page is essentially empty (all sub-pages just show "Connect wallet"), so there is no schema documentation, no example request/response payloads, and no detailed API reference available. The actual content returned by the receipt endpoint is unknown beyond its declared MIME type of application/json.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 158 via programmatic payment
- —Demonstrating x402 protocol payment flows on Base
- —Agent-driven micropayment API consumption without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need to fetch transaction receipts without pre-registration
- —Use cases requiring keyless, pay-per-call API access on Base
Not for
- —Production workloads requiring documented schemas and SLAs
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users who need fiat-only payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/158/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment on Base to complete.Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is zero documentation beyond the landing page — no OpenAPI spec, no request/response schemas, no examples. The specific resource (transaction 158 receipt) is narrow and unexplained. All doc/pricing/API sub-pages return only 'Connect wallet' with no content.
Warnings
- —No API documentation available — all doc pages return only 'Connect wallet'
- —No request or response schema provided for this endpoint
- —The endpoint is for a specific transaction ID (158); unclear if other transaction IDs are available or how they are discovered
- —The broader platform lists many API categories but none have documented schemas or examples
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/158/receipt
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/158/receipt