x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 145) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).
The broader lowpaymentfee.com platform advertises a wide catalog 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. However, the specific endpoint being listed here is a single transaction receipt resource, and no documentation was found describing the schema of the receipt response or what data it contains.
The probe confirmed the endpoint is live, returning a proper 402 challenge with x402 version 1. The site's docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content, so details about request/response formats remain unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 145 via a single paid API call
- —Demonstrating x402 payment flow integration on Base with USDC
- —Agent-driven micropayment API consumption without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to make small USDC-denominated API purchases
- —Projects exploring keyless, pay-per-call API access patterns
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk or high-volume receipt retrieval (no batch endpoint documented)
- —Users who need fiat-only payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/145/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming pricing and network details. However, there is no documentation for the request body, response schema, or what the receipt actually contains. The docs/pricing/README pages are all empty beyond a wallet-connect prompt. This is effectively a stub listing with confirmed liveness but no usable API documentation.
Warnings
- —No API documentation available — docs, pricing, and README pages return only 'Connect wallet' with no content.
- —Response schema for the receipt endpoint is completely unknown.
- —This endpoint is for a single hardcoded transaction ID (145); unclear if other transaction IDs are available or how they are discovered.
- —The broader platform advertises many endpoints (AI, finance, analytics, etc.) but none were probed; only this single receipt endpoint is confirmed live.
Citations
- —The endpoint returns a 402 challenge with x402 version 1, scheme 'exact', on Base network using USDC at max amount 20000 base units.https://lowpaymentfee.com/api/v1/transactions/145/receipt
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/transactions/145/receipt
- —All endpoints listed at $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —Platform advertises APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categories.https://lowpaymentfee.com