Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/272/receipt`. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all settled via the x402 protocol on the Base network using USDC.
The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call. Payment is made via the x402 "exact" scheme to the specified wallet address. The platform advertises a flat $0.02 per request 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 further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt endpoint actually returns. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what data is returned or what input parameters (if any) are expected in the POST body.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID
- —Programmatic proof-of-payment or audit trail retrieval
- —Agent-driven workflows that need transaction confirmation data
Fit
Best for
- —Developers wanting keyless, pay-per-call API access on Base
- —Agents that can settle USDC payments via x402 protocol
- —Use cases requiring low-cost ($0.02) per-request pricing with no commitments
Not for
- —Users needing detailed API documentation or request/response schemas before integrating
- —High-volume batch processing where per-call costs add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/272/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it works. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the specific purpose of this receipt endpoint (transaction 272) is unclear. The platform lists many endpoints but provides no detail on any of them.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all render only 'Connect wallet'
- —No OpenAPI or output schema provided for the receipt endpoint
- —The endpoint path includes a hardcoded transaction ID (272), which may indicate a demo or specific-use resource rather than a general-purpose API
- —No request body schema documented; unclear what POST body is expected
- —No response examples or schema available
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/272/receipt
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/272/receipt
- —Documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs