Pay-per-call transaction receipt endpoint on Base via x402, $0.02/request in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt retrieval service accessible via the x402 payment protocol. The specific resource `/api/v1/transactions/134/receipt` returns a JSON receipt for transaction ID 134, gated behind a per-request USDC payment on the Base network.
The provider operates a broader platform offering multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities—all priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payment is settled on-chain using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base.
The x402 challenge confirms the endpoint is live, accepting POST requests with an exact payment scheme. The maxAmountRequired of 20000 base units (USDC has 6 decimals) equals $0.02 per call. The payment timeout is 300 seconds. No OpenAPI schema, detailed documentation, or example responses were found beyond the landing page listing.
Capabilities
Use cases
- —Retrieving transaction receipts programmatically with per-call payment
- —Integrating pay-as-you-go APIs without subscription or API key management
- —Agent-driven workflows that need on-chain payment verification for transactions
Fit
Best for
- —Developers wanting zero-commitment API access paid in USDC
- —AI agents that can settle x402 payments autonomously on Base
- —Projects needing transaction receipt data without account setup
Not for
- —High-volume batch processing where per-call fees add up quickly
- —Users without a Base-compatible wallet or USDC holdings
- —Applications requiring detailed API documentation or SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/134/receipt \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via 402 challenge and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documented request/response format, no example payloads, and the docs/pricing/README pages all render only a wallet-connect prompt with no useful content. The specific purpose of 'transaction 134 receipt' is opaque.
Warnings
- —No API documentation available—docs, pricing, and README pages only show a wallet-connect prompt
- —No request or response schema documented; actual output format is unknown
- —The endpoint path references a specific transaction ID (134), unclear if this is parameterized or fixed
- —Provider platform appears to list many endpoints but none have visible documentation beyond titles
Citations
- —Endpoint returns 402 with x402 challenge requiring 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/134/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/134/receipt