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 (transaction ID 192) behind an x402 paywall. 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 utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/192/receipt` accepts POST requests and returns an `application/json` response. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header containing a signed payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to the merchant address `0x1A2B…85F3`. The payment scheme is "exact" with a 300-second timeout window. No API keys or rate limits are advertised; access is purely gated by micropayment.
Documentation on the site is extremely sparse — the docs, pricing, API, 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 example payloads available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data returned after payment is unknown. The platform lists many other endpoints across categories like sentiment analysis, text summarization, geocoding, and crypto gas estimates, all at the same $0.02 price point.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 192 via micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand transaction receipts via crypto micropayments
- —Use cases requiring keyless, pay-as-you-go API access on Base
Not for
- —Users needing detailed API documentation or request/response schemas before integrating
- —High-volume batch retrieval where per-call pricing is inefficient
- —Users without access to USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/192/receipt \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The docs pages render only 'Connect wallet' with no content. The actual data returned after payment is completely unknown, making this effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema for request or response bodies
- —The specific resource (transaction 192 receipt) purpose and contents are unknown
- —No examples of successful responses available
- —Platform lists many endpoints but none have documented schemas
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/192/receipt
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/192/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs