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 72) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) via the x402 "exact" scheme.
The specific endpoint `/api/v1/transactions/72/receipt` costs $0.02 per request (maxAmountRequired of 20,000 base units with USDC's 6 decimals). The broader lowpaymentfee.com platform advertises a suite of x402-gated APIs spanning data & analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all at the same $0.02/request price point. The platform emphasizes no API keys, no rate limits, and instant access.
However, the specific endpoint being listed here is a transaction receipt resource, which does not clearly map to any of the advertised API categories. Documentation pages (/docs, /pricing, /README) returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation available for this or any other endpoint on the platform. The endpoint is confirmed live via a valid 402 challenge.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 72 via a single paid API call
- —Demonstrating x402 payment protocol integration with USDC on Base
- —Agent-driven programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access without authentication setup
- —Use cases requiring USDC micropayments on Base L2
Not for
- —Bulk retrieval of many transaction receipts (no batch endpoint documented)
- —Users needing detailed API documentation or OpenAPI specs before integration
- —Production workloads requiring SLA guarantees or documented error handling
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/72/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (valid 402 challenge captured), but there is no documentation, no OpenAPI schema, no request/response examples, and the endpoint path (transactions/72/receipt) is a single hardcoded resource with unclear utility. Doc pages return only wallet-connect prompts.
Warnings
- —No OpenAPI schema or API documentation available — all doc pages return only 'Connect wallet'
- —The endpoint path references a specific transaction ID (72); unclear if this is a demo or a real resource
- —No request body schema or response schema documented anywhere
- —The platform advertises many API categories but none match 'transaction receipt' specifically
- —No error handling, rate limit, or SLA information available
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base network, maxAmountRequired 20000https://lowpaymentfee.com/api/v1/transactions/72/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/72/receipt
- —Documentation pages (/docs, /pricing, /README) return only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs