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/371/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 utility services — 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 a designated wallet address. The platform advertises a flat $0.02 per request across all endpoints, with no API keys, no rate limits, and instant access.
Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the transaction receipt endpoint actually returns. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to determine the exact payload format or use case for this specific resource. The broader site lists many endpoint categories but provides no further technical detail beyond names and prices.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID via micropayment
- —Programmatic access to receipt data without API key management
- —Agent-driven workflows that need on-demand transaction documentation
Fit
Best for
- —Developers wanting keyless, pay-per-call API access on Base
- —AI agents that can settle x402 payments autonomously
- —Users who need low-cost, no-commitment API calls
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Bulk or high-throughput use cases where per-call pricing may add up
- —Anyone needing non-USDC or non-Base-network payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/371/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid USDC payment to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the receipt resource contains. The site's docs/pricing/API pages are all blank beyond a wallet connect prompt. This is effectively a stub listing.
Warnings
- —No OpenAPI schema or endpoint documentation available
- —Docs, pricing, API, and README pages all render only 'Connect wallet' with no content
- —No request or response examples available — payload format is unknown
- —The specific resource '/api/v1/transactions/371/receipt' is hardcoded to transaction ID 371; unclear if other IDs are supported or how to discover them
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/371/receipt
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The site lists APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com