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 (transaction ID 96) behind an x402 paywall. It is part of a broader platform that advertises multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all gated via the x402 protocol on the Base network and settled in USDC.
The specific endpoint `/api/v1/transactions/96/receipt` accepts POST requests and returns `application/json`. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 per request (USDC uses 6 decimals). The platform advertises uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments required.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The endpoint is confirmed live (402 challenge captured), but the actual functionality behind this particular receipt endpoint is unclear beyond its name. The platform lists many other endpoints (analytics, AI inference, finance, utilities) but none have documented schemas or example payloads.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 96 via a single paid API call
- —Programmatic access to receipt data without API key registration
- —Agent-driven workflows that need on-chain-settled receipt retrieval
Fit
Best for
- —Developers wanting keyless, pay-per-call API access on Base
- —AI agents that can settle x402 payments in USDC
- —Quick one-off receipt lookups without subscription overhead
Not for
- —Bulk or high-volume receipt retrieval where per-call costs add up
- —Users who need detailed API documentation or SDKs before integrating
- —Anyone needing receipts for arbitrary transaction IDs (this endpoint is scoped to ID 96)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/96/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02/call in USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the actual functionality of this specific receipt endpoint is opaque. The listing is effectively a stub.
Warnings
- —No OpenAPI spec or schema documentation available
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
- —The endpoint is scoped to a single transaction ID (96); unclear if this is a demo or production resource
- —No request body schema or response schema documented anywhere
- —Platform lists many endpoint categories but none have verifiable documentation
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/96/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/96/receipt
- —Platform lists endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com