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 283) 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 (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, with no API keys, no rate limits, and no minimum commitments.
The specific endpoint probed (/api/v1/transactions/283/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base, 6 decimals), which equals $0.02. Payment is made via the x402 "exact" scheme to the specified payTo address. The endpoint accepts POST requests and returns application/json. Documentation pages (docs, pricing, README) appear to be behind a wallet-connect gate and contain no substantive content.
While the platform lists many endpoints, this particular listing covers only the transaction receipt resource. No OpenAPI schema, request/response examples, or detailed documentation were available from the crawl. The actual data returned by this receipt endpoint is unknown — it could be a blockchain transaction receipt, a payment confirmation, or something else entirely. Prospective callers should be aware that the endpoint's purpose is inferred solely from its URL path.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 283 via a single micropayment
- —Programmatic access to receipt data without API key registration
- —Agent-driven workflows that need to fetch and verify transaction records on demand
Fit
Best for
- —Agents or scripts that need one-off transaction receipt lookups
- —Developers exploring x402 pay-per-call patterns on Base
- —Use cases where avoiding API key management is preferred
Not for
- —Bulk or batch retrieval of many transaction receipts (only one transaction ID is served)
- —Users who need detailed API documentation or response schema guarantees before calling
- —Free-tier or non-crypto payment workflows
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/283/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI schema, no documentation, no request/response examples, and the actual purpose of this specific receipt endpoint is unclear. The broader platform lists many APIs but docs pages are empty behind a wallet gate.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —Documentation, pricing, and README pages are gated behind wallet-connect and contain no content
- —The specific data returned by /api/v1/transactions/283/receipt is unknown — purpose inferred only from URL path
- —This endpoint serves a single hardcoded transaction ID (283); unclear if other IDs are available at similar paths
Citations
- —The platform lists APIs across data & analytics, AI/ML, finance & Web3, and infrastructure, all priced at $0.02/requesthttps://lowpaymentfee.com
- —Pricing is $0.02 per request with no API keys, no rate limits, instant access, on Base networkhttps://lowpaymentfee.com
- —The x402 challenge specifies maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/transactions/283/receipt