x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 207) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network, with no API keys, no rate limits, and no commitments required.
The specific endpoint probed (/api/v1/transactions/207/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the site's advertised pricing. The payment scheme is "exact" with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
Documentation is extremely thin — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The nature of what the "transaction receipt" contains is not documented, making it difficult to assess the endpoint's practical utility without experimentation.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 207 via a single micropayment
- —Demonstrating x402 protocol payment flows on Base
- —Agent-driven pay-per-use API consumption without API keys
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call API access on Base
- —Testing USDC micropayment integrations
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk transaction receipt retrieval across many transaction IDs
- —Users who need traditional API key authentication or free-tier access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/207/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof to access.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The purpose of the specific receipt endpoint is unclear, and all doc pages return only a wallet-connect prompt.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README all render only 'Connect wallet'
- —No OpenAPI or schema definition found for request or response payloads
- —The specific endpoint (/api/v1/transactions/207/receipt) purpose is undocumented; unclear what data the receipt contains
- —The broader platform advertises many API categories but none could be verified beyond the landing page descriptions
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/207/receipt
- —All endpoints 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
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/207/receipt