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 242) behind an x402 paywall. It is part of a broader platform that advertises multiple API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/242/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol (version 1, "exact" scheme): the caller must include an X-PAYMENT header encoding a USDC payment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals) to the specified payTo address on Base. No API keys or rate limits are advertised; access is purely pay-per-call.
Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 outputSchema stub, and no explanation of what the receipt payload contains. The endpoint is confirmed live (402 challenge captured), but the actual utility and response format remain unclear.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 242 via a micropayment
- —Demonstrating x402 protocol payment flow on Base
- —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
- —Users who need free or subscription-based API access
- —Bulk data retrieval where per-call pricing is impractical
Quick start
# The endpoint requires an X-PAYMENT header with a valid x402 USDC payment on Base.
curl -X POST https://lowpaymentfee.com/api/v1/transactions/242/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what the receipt contains. The listing is a stub with confirmed liveness but very little actionable information.
Warnings
- —No documentation available — docs, API, pricing, and README pages all render only 'Connect wallet'
- —No OpenAPI or JSON schema describing request body or response format
- —The specific resource (transaction 242 receipt) is opaque — unclear what data is returned
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/242/receipt
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/242/receipt