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 95) 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/95/receipt` accepts POST requests and returns `application/json`. 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 or rate limits are advertised; access is purely pay-per-use.
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 spec, no request/response schema beyond the x402 challenge's `outputSchema`, and no description of what the receipt payload actually contains. The platform lists many endpoints across several domains, but without documentation it is unclear what data each returns or whether they are fully functional.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 95 via a micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that can settle USDC on Base for per-call API access
- —Use cases requiring keyless, pay-as-you-go API consumption
Not for
- —Users needing detailed API documentation or response schemas before integrating
- —Bulk or high-volume receipt retrieval where per-call pricing is inefficient
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/95/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 (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI spec, no request body schema, and no example response. The purpose of this specific receipt endpoint is unclear beyond its URL path. Effectively a stub listing.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or request/response schema provided
- —Purpose and contents of the transaction receipt are unknown
- —The endpoint is for a specific transaction ID (95); unclear if this is a demo or a real resource
- —Platform lists many endpoints but none have documented behavior
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/95/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/95/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs