Transaction receipt retrieval via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource `/api/v1/transactions/257/receipt`) behind an x402 paywall. Payment is settled in USDC on the Base network at $0.02 per request (maxAmountRequired of 20,000 base units with USDC's 6 decimals). The endpoint accepts POST requests and returns JSON.
The broader lowpaymentfee.com platform advertises a suite of x402-gated APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The specific endpoint probed here (`/transactions/257/receipt`) is not listed on the homepage's API catalog, so its purpose and response format are unclear beyond the generic "Premium API Access" label.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID via micropayment
- —Programmatic access to receipt data without API key registration
- —Agent-driven payment-gated data retrieval on Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need on-demand receipt data without pre-registration
- —Low-friction pay-per-use API consumption on Base
Not for
- —Production use requiring documented request/response schemas
- —Bulk or high-volume receipt retrieval where per-call pricing is inefficient
- —Users who need detailed API documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/257/receipt
# Returns 402 with x402 payment challenge.
# Include X-PAYMENT header with valid USDC payment proof on Base to access the resource.Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The specific endpoint path (/transactions/257/receipt) is not listed in the site's own catalog, and all doc pages return only 'Connect wallet' with no content. This is effectively a stub listing.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet'
- —No OpenAPI or schema definition found for any endpoint
- —The specific endpoint /api/v1/transactions/257/receipt is not listed in the site's own API catalog
- —Request body format and response schema are completely unknown
- —Platform appears to be a demo or early-stage project with placeholder documentation
Citations
- —The endpoint returns a 402 challenge requiring USDC payment on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/transactions/257/receipt
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/257/receipt
- —All listed APIs are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) contain only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs