Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 135) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD.
The provider's landing page advertises a broader 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 priced uniformly at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, this specific endpoint is scoped to `/api/v1/transactions/135/receipt`, which appears to be a single transaction receipt resource rather than a general-purpose API.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no detailed documentation describing what the receipt payload contains or what parameters the POST body accepts. The endpoint is confirmed live (returns a valid x402 402 challenge), but the actual functionality behind the paywall is unclear.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 135 via programmatic pay-per-call access
- —Demonstrating x402 payment protocol integration on the Base network
- —Agent-driven micropayment workflows settling in USDC
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access without API key management
- —Use cases requiring USDC micropayments on Base
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk transaction receipt retrieval across many transaction IDs
- —Users who need detailed API documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/135/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and the specific endpoint path (/transactions/135/receipt) suggests a single hardcoded resource rather than a parameterized API. The broader site advertises many endpoints but none are documented.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet'
- —No OpenAPI or schema definition provided for request or response payloads
- —Endpoint path references a specific transaction ID (135); unclear if this is parameterized or a single fixed resource
- —The broader suite of advertised APIs (AI, analytics, finance, utilities) could not be verified beyond the landing page listing
- —No robots.txt or agents.txt present
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/135/receipt
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider advertises APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimalshttps://lowpaymentfee.com/api/v1/transactions/135/receipt