x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource behind an x402 payment wall. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/360/receipt` accepts POST requests and returns an `application/json` response. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using the "exact" scheme with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.
Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no explanation of what data the receipt endpoint actually returns. The platform lists many other endpoints (sentiment analysis, summarization, geocoding, etc.) but provides no detailed documentation for any of them. Treat this listing as a stub until richer docs surface.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 360 via a single paid API call
- —Demonstrating x402 payment-gated API access on the Base network
- —Integrating pay-per-request infrastructure into agent workflows without API keys
Fit
Best for
- —Agents or developers experimenting with x402 payment protocols
- —Use cases requiring keyless, pay-per-call API access on Base
- —Prototyping micropayment-gated data retrieval
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based API access
- —High-throughput batch processing where per-call payment overhead is impractical
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/360/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, and all documentation pages render only a wallet-connect prompt. The purpose of the specific receipt endpoint is unclear beyond its URL path. This is effectively a stub listing.
Warnings
- —No OpenAPI or detailed documentation available — all doc pages render only 'Connect wallet'
- —No request body schema or response schema documented for this endpoint
- —The purpose and data returned by /api/v1/transactions/360/receipt is not explained anywhere
- —The endpoint path includes a hardcoded transaction ID (360); it is unclear if this is parameterized or fixed
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/360/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 offers endpoints across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimalshttps://lowpaymentfee.com/api/v1/transactions/360/receipt