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 344) 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 suite of APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (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, this specific listing is for the `/api/v1/transactions/344/receipt` endpoint only, which is not among the advertised categories on the landing page.
Documentation 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 spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (returns a valid x402 402 challenge), but the actual content and structure of the receipt response are unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 344 via programmatic pay-per-call access
- —Demonstrating x402 payment protocol integration for agent-to-agent commerce
- —Testing USDC micropayment flows on the Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access without API key management
- —Use cases requiring USDC-settled micropayments on Base
Not for
- —Production workloads requiring well-documented request/response schemas
- —Bulk transaction receipt retrieval (this endpoint is scoped to a single transaction ID)
- —Users who need fiat payment options or non-crypto settlement
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/344/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no examples. The endpoint path (/transactions/344/receipt) is hardcoded to a single transaction ID and is not listed among the platform's advertised APIs, making its purpose unclear. Score reflects minimal usable information beyond the payment challenge itself.
Warnings
- —No OpenAPI spec or schema documentation available
- —The /docs, /pricing, /api, and /README pages contain no useful content beyond a wallet connect prompt
- —This specific endpoint (/api/v1/transactions/344/receipt) is not listed among the platform's advertised API categories — its purpose and response format are unknown
- —Request and response body schemas are completely undocumented
- —Endpoint is scoped to a single hardcoded transaction ID (344), which may indicate a demo or test resource
Citations
- —The endpoint returns a valid x402 402 challenge with USDC on Base network, maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/transactions/344/receipt
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/344/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) render only a Connect wallet prompthttps://lowpaymentfee.com/docs