Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt retrieval service behind an x402 paywall. When called via POST, it returns a JSON receipt for transaction ID 129. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (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 required. Payment is handled entirely through the x402 protocol on the Base L2 network.
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 usage examples available from the crawled material. The specific endpoint probed (/api/v1/transactions/129/receipt) is live and returns a valid x402 challenge, but its actual response payload structure is unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID
- —Programmatic proof-of-payment or audit trail retrieval
- —Agent-driven workflows that need verifiable transaction records
Fit
Best for
- —Agents needing on-demand transaction receipts without API key management
- —Micropayment-settled receipt lookups on Base L2
- —Workflows requiring no-signup, instant-access API calls
Not for
- —Bulk or batch receipt retrieval (no documented batch endpoint)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto-native callers who cannot settle USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/129/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, confirming it is operational. However, there is no OpenAPI spec, no documented request/response schema, no usage examples, and the docs pages are all empty wallet-connect stubs. The specific endpoint path (/transactions/129/receipt) suggests a hardcoded resource rather than a parameterized API. Very little can be verified about what the endpoint actually returns.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README all show only 'Connect wallet' with no content.
- —No OpenAPI or JSON schema describing request parameters or response format.
- —The endpoint path includes a hardcoded transaction ID (129); it is unclear whether other transaction IDs are supported or how to discover them.
- —The broader platform lists many endpoints (AI, finance, utilities) but none could be verified beyond the landing page descriptions.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Base network.https://lowpaymentfee.com/api/v1/transactions/129/receipt
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The platform lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categories.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/transactions/129/receipt