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 280) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request 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 priced at $0.02 per request, settled in USDC on the Base network, with no API keys, no rate limits, and no minimum commitments.
The specific endpoint probed (/api/v1/transactions/280/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base, 6 decimals), which equals $0.02. Payment is made via the x402 "exact" scheme to the specified payTo address. The endpoint accepts POST requests and returns application/json. No OpenAPI spec, detailed documentation, or example responses were found during crawling — the docs, pricing, API, and README pages all rendered only a "Connect wallet" prompt with no substantive content.
Because this is a single transaction receipt endpoint rather than a general-purpose API, its utility to most agents is narrow. The platform's broader API catalog (AI, finance, utilities) may be more broadly useful, but those endpoints were not individually probed. The lack of documentation, schemas, or example payloads significantly limits the ability to assess what the receipt response contains or how to construct valid requests.
Capabilities
Use cases
- —Retrieving a receipt for transaction 280 via a micropayment-gated API call
- —Demonstrating x402 payment flow on Base with USDC
- —Programmatic access to transaction data without API key registration
Fit
Best for
- —Agents exploring x402 payment protocol integration
- —Developers testing micropayment-gated API patterns on Base
- —Scenarios requiring keyless, pay-per-use API access
Not for
- —Bulk transaction data retrieval (this is a single receipt endpoint)
- —Users who need detailed API documentation or schemas before integrating
- —Free or subscription-based API access patterns
Quick start
# 1. POST to the endpoint — you'll get a 402 with payment challenge
curl -X POST https://lowpaymentfee.com/api/v1/transactions/280/receipt
# 2. Pay the x402 challenge (20000 base units USDC = $0.02 on Base)
# then include the X-PAYMENT header with your payment proof
curl -X POST https://lowpaymentfee.com/api/v1/transactions/280/receipt \
-H "X-PAYMENT: <your-x402-payment-token>"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint works and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a wallet-connect prompt, no example request/response payloads, and the specific endpoint is a single transaction receipt with unclear utility. The listing is essentially a stub with confirmed liveness.
Warnings
- —No OpenAPI or schema documentation available — request/response formats are unknown
- —Docs, pricing, API, and README pages all render only 'Connect wallet' with no content
- —This endpoint is for a specific transaction receipt (ID 280); general-purpose utility is unclear
- —The broader platform advertises many endpoints but none were individually verified beyond this one
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/280/receipt
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/280/receipt
- —Platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Basehttps://lowpaymentfee.com
- —Platform offers APIs across data & analytics, AI/ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com