x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource via the x402 payment protocol. The specific path `/api/v1/transactions/56/receipt` returns a receipt for transaction ID 56 in JSON format, gated behind a per-request USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live and accepts exact-scheme payments of up to 20,000 base units of USDC (0.02 USD) per call, with a 300-second payment timeout.
The broader lowpaymentfee.com platform advertises a suite of x402-gated APIs spanning data & analytics (metrics, reports, data export, insights), AI & ML (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. Payments settle in USDC on the Base L2 network.
Documentation beyond the landing page 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 schema, no request/response examples, and no description of what the transaction receipt payload actually contains. The endpoint is confirmed live via the 402 challenge, but the lack of documentation makes it difficult to assess the actual utility or data quality of the response.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID via micropayment
- —Programmatic access to transaction data without API key registration
- —Agent-driven workflows that need pay-per-call receipt retrieval on Base
Fit
Best for
- —Developers experimenting with x402 payment protocol integrations
- —Agents that need keyless, pay-per-use API access on Base
- —Prototyping micropayment-gated data retrieval
Not for
- —Production use cases requiring documented request/response schemas
- —Bulk or high-volume receipt retrieval where per-call costs add up
- —Users who need detailed API documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/56/receipt
# Returns 402 with x402 payment challenge.
# Include X-PAYMENT header with a valid USDC payment proof on Base to receive the receipt.Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, but there is no OpenAPI schema, no request/response examples, and no meaningful documentation beyond a landing page listing. The specific resource (transaction 56 receipt) is narrow and unexplained. Score reflects a functional but essentially undocumented stub.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The endpoint path references a hardcoded transaction ID (56); unclear if this is parameterized or fixed
- —No information on what data the receipt contains or its accuracy/freshness
Citations
- —Endpoint returns 402 with x402 challenge accepting USDC on Base network, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/transactions/56/receipt
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Platform lists APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/56/receipt