x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (specifically for transaction ID 33) behind an x402 paywall. The site advertises itself as a platform hosting multiple pay-per-request API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/33/receipt` returns a JSON response upon payment. The x402 challenge confirms the endpoint is live, accepting POST requests, and requires an exact payment of 20,000 base units of USDC (0x8335…2913 on Base, which is 6 decimals → $0.02). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is gated purely by the x402 micropayment.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no description of what the receipt payload actually contains. The broader site lists many endpoints across multiple categories, but this specific listing covers only the transaction receipt resource.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 33 via micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agent-driven on-chain payment for data retrieval
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need to fetch transaction receipts without API keys
- —Testing USDC micropayment flows on Base
Not for
- —Production use requiring documented response schemas and SLAs
- —Bulk or batch transaction receipt retrieval (single resource only)
- —Users who need free or subscription-based access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/33/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — no OpenAPI spec, no response schema, no explanation of what the receipt contains. The endpoint path is hardcoded to a single transaction ID (33), making its general utility unclear. Pricing is clear ($0.02 USDC on Base) but everything else must be inferred.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
- —No OpenAPI or response schema provided; the actual receipt payload structure is unknown
- —Endpoint is hardcoded to transaction ID 33 — unclear if other transaction IDs are supported or what this transaction represents
- —The broader site lists many endpoint categories but none have documented schemas or examples
Citations
- —Endpoint returns 402 with x402 challenge requiring 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/33/receipt
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimals, so 20000 base units = $0.02https://lowpaymentfee.com/api/v1/transactions/33/receipt
- —Site advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Multiple API categories listed: Data & Analytics, AI & ML, Finance & Web3, Infrastructurehttps://lowpaymentfee.com