x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 176) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network via the x402 protocol.
The specific endpoint probed (/api/v1/transactions/176/receipt) returns a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this equals $0.02 per call, consistent with the site's advertised pricing. Payment is made via the x402 "exact" scheme to the specified payTo address. No API keys or rate limits are required — access is purely payment-gated.
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 documentation, and no examples of what the receipt payload actually contains. The endpoint accepts POST requests and returns application/json, but the structure of both the request body and response is unknown.
Capabilities
Use cases
- —Retrieving transaction receipt data for transaction 176 via a single micropayment
- —Programmatic access to paid API endpoints without managing API keys or subscriptions
- —Agent-driven workflows that need to pay-per-call for data retrieval on Base
Fit
Best for
- —Developers or agents wanting keyless, pay-per-use API access
- —Use cases requiring USDC micropayments on Base L2
- —Scenarios where subscription-free, on-demand data access is preferred
Not for
- —Users needing detailed API documentation or guaranteed SLAs
- —Bulk data retrieval where per-request pricing would be cost-prohibitive
- —Users without access to USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/176/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no examples. The purpose of this specific receipt endpoint is unclear beyond its URL path. The broader platform lists many endpoints but provides no docs for any of them.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
- —No OpenAPI or schema definition found for any endpoint on the platform
- —The specific endpoint (/api/v1/transactions/176/receipt) appears to be for a single hardcoded transaction ID; unclear if this is a general-purpose endpoint
- —Request body schema and response payload structure are completely unknown
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/176/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform offers APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/176/receipt