Pay-per-call transaction receipt endpoint on Base via x402, settled 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 187) 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, which equals $0.02 (USD Coin uses 6 decimals). The endpoint returns application/json.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call 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, the specific endpoint being listed here is scoped to a single transaction receipt resource.
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 crawl. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the actual response payload structure after payment is unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 187 via a single micropayment
- —Demonstrating x402 payment protocol integration on the Base network
- —Agent-driven pay-per-call data retrieval without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access on Base
- —Testing USDC micropayment flows
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk transaction receipt retrieval across many transaction IDs
- —Users who need fiat-only payment rails
Quick start
# The endpoint requires an x402 payment header (USDC on Base).
# 1. POST to the endpoint without payment to receive the 402 challenge:
curl -X POST https://lowpaymentfee.com/api/v1/transactions/187/receipt
# 2. Use an x402-compatible client to fulfill the payment challenge
# (maxAmountRequired: 20000 base units = $0.02 USDC on Base)Endpoint
Quality
The endpoint is confirmed live via a valid 402 x402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no usage examples, and the docs pages are empty. The endpoint is scoped to a single transaction ID (187) with no explanation of what the receipt contains or how to use other transaction IDs.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) are all empty beyond a 'Connect wallet' prompt
- —No OpenAPI or schema documentation available
- —No example request or response payloads documented
- —Endpoint is hardcoded to transaction ID 187 — unclear if other IDs are supported
- —The platform lists many other API categories (AI, analytics, finance, infrastructure) but none were probed for liveness
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/187/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 platform advertises APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages render only a 'Connect wallet' prompt with no technical contenthttps://lowpaymentfee.com/docs