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 80) 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 priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/80/receipt` accepts POST requests and returns an `application/json` response. Payment is handled via the x402 protocol: callers receive a 402 challenge specifying the USDC asset on Base (contract `0x8335…2913`), and must attach an `X-PAYMENT` header with a valid payment proof. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02 per call. No API keys, rate limits, or subscriptions are needed — access is purely pay-per-request.
Documentation on the site is extremely thin. 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 payload actually contains. The platform lists many other endpoints across analytics, AI, finance, and utility categories, but this specific listing covers only the transaction receipt resource. Without documentation on the response schema, callers should expect a JSON object but cannot know its structure in advance.
Capabilities
Use cases
- —Retrieving a receipt for transaction ID 80 via programmatic pay-per-call access
- —Demonstrating x402 protocol integration for USDC micropayments on Base
- —Agent-driven retrieval of transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need keyless, pay-per-request access to transaction receipts
- —Projects already operating on the Base L2 network with USDC
Not for
- —Users needing well-documented API schemas and response examples
- —Bulk or high-volume transaction data retrieval (no documented batch support)
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/80/receipt
# Returns 402 with x402 challenge. Attach X-PAYMENT header with valid USDC payment proof on Base to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no response schema documentation, no request body documentation, and all doc pages render only 'Connect wallet'. The purpose of this specific receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet'
- —No OpenAPI or schema definition for request or response payloads
- —The specific resource (transaction 80 receipt) is not explained anywhere on the site
- —The broader platform lists many endpoints but none have documented schemas
- —Cannot verify what data the receipt actually returns without paying
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/80/receipt
- —The platform advertises $0.02 per request across all endpoints 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/80/receipt