Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt for transaction ID 329. It is part of a broader platform offering multiple pay-per-call 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 commitments required.
The specific endpoint `/api/v1/transactions/329/receipt` accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) via the x402 "exact" scheme. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a maximum timeout of 300 seconds.
Documentation on the site is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI schema, no request/response examples, and no detailed documentation for what the receipt endpoint actually returns. The platform's landing page lists many endpoints across several categories, but the specific behavior and response format of this particular receipt endpoint is undocumented.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 329 via a single paid API call
- —Demonstrating x402 pay-per-call patterns on the Base network
- —Integrating USDC micropayments into agent workflows without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents needing keyless, pay-per-call API access on Base
- —Use cases requiring low-cost ($0.02) per-request pricing with no subscription
Not for
- —Production workloads requiring documented response schemas and SLAs
- —Bulk or high-volume receipt retrieval where per-call pricing is inefficient
- —Users who need fiat-only payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/329/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and the docs pages are empty. The purpose of a receipt for a hardcoded transaction ID 329 is unclear, making this effectively a stub listing.
Warnings
- —No OpenAPI schema or API documentation available — all doc pages render only 'Connect wallet'
- —The endpoint path contains a hardcoded transaction ID (329); it is unclear whether this is parameterized or fixed
- —No request body schema or response schema is documented anywhere
- —The broader platform lists many endpoints but none appear to have detailed documentation
Citations
- —The endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/329/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform offers endpoints across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and payTo is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/transactions/329/receipt