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 (transaction ID 225) behind an x402 paywall. The provider operates a broader platform offering multiple API categories — 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/225/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers receive a 402 challenge containing payment details (payTo address, asset contract, amount), construct an on-chain USDC payment on Base, and include the payment proof in the `X-PAYMENT` header to gain access. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. No API keys, rate limits, or upfront commitments are required.
Documentation on the site 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 description of what the receipt payload actually contains. The endpoint is live and responding with a valid x402 challenge, but the lack of documentation makes it difficult to know what data is returned or what inputs (if any) the POST body expects.
Capabilities
Use cases
- —Retrieving a receipt for transaction 225 via programmatic micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agents autonomously purchasing transaction data without API keys
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need to fetch transaction receipts without pre-registration
- —Use cases requiring low-cost, keyless API access on Base
Not for
- —Bulk retrieval of many different transaction receipts (only transaction 225 is exposed at this endpoint)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Non-crypto workflows that cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/225/receipt
# Returns 402 with x402 challenge. Include X-PAYMENT header with USDC payment proof on Base to access.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — docs/pricing/API pages all show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no description of what the receipt contains or what POST body is expected. The endpoint path is specific to a single transaction ID (225), which limits general utility.
Warnings
- —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content
- —No OpenAPI or schema available — request body and response format are unknown
- —Endpoint is specific to transaction ID 225; unclear if other transaction IDs are available at similar paths
- —Provider platform lists many other endpoints but none were probed; their functionality is unverified
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/225/receipt
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform offers APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/225/receipt