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 157) 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/157/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 exact-payment scheme: the caller must attach an `X-PAYMENT` header with a signed USDC payment on Base (contract `0x8335…2913`). The maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02 per call. No API keys, rate limits, or upfront commitments are required — 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 explanation of what the receipt payload actually contains. The platform lists many endpoints across different domains but provides no detail on inputs, outputs, or data sources for any of them. Treat this as a low-documentation endpoint where the actual response structure is unknown until you make a paid call.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 157 via a single paid API call
- —Demonstrating x402 payment flow integration on Base with USDC
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to fetch transaction receipts via micropayments
- —Projects wanting key-less, pay-per-use API access
Not for
- —Production use cases requiring documented request/response schemas
- —Bulk retrieval of many different transaction receipts (only transaction 157 is exposed at this URL)
- —Users who need free or subscription-based API access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/157/receipt \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-H "Content-Type: application/json"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 documented request/response schema, no examples, and all documentation pages render only a wallet-connect prompt. The specific purpose of this receipt endpoint is unclear beyond its URL path.
Warnings
- —No OpenAPI or schema documentation available — response structure is entirely unknown
- —All doc/pricing/README pages return only a 'Connect wallet' prompt with no useful content
- —This URL is scoped to a single transaction ID (157); unclear if other transaction IDs are available
- —The platform lists many endpoint categories but provides zero detail on any of them
- —No information on data sources, accuracy, or freshness of any API responses
Citations
- —The endpoint returns a 402 challenge with x402Version 1, exact scheme, on Base network, requiring up to 20000 base units of USDC (USD Coin)https://lowpaymentfee.com/api/v1/transactions/157/receipt
- —The platform advertises $0.02 per request pricing 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/157/receipt