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 168) 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 infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/168/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The challenge advertises a `maxAmountRequired` of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout. No API keys or rate limits are advertised; access is purely gated by micropayment.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples. The platform lists many other endpoints (analytics, AI, finance, utils) at the same $0.02 price point, but details about what data this particular receipt endpoint returns are not documented.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 168 via micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Agent-driven data retrieval without API key management
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need keyless, pay-per-call API access on Base
- —Projects requiring USDC-settled micropayment API patterns
Not for
- —Production use cases requiring documented request/response schemas
- —Bulk or high-volume data retrieval (no batch endpoints documented)
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/168/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-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 documentation, no OpenAPI spec, no request/response schema, and no examples. The docs pages all render only 'Connect wallet' with no content. The specific purpose of this receipt endpoint is undocumented.
Warnings
- —No OpenAPI spec or schema documentation available
- —Docs, pricing, API, and README pages all render only 'Connect wallet' with no substantive content
- —No request body schema or response schema documented — callers cannot know what to send or expect back
- —The endpoint path references a specific transaction ID (168); unclear if this is a generic pattern or a single fixed resource
- —Platform lists many endpoints but none appear to have detailed documentation
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/168/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 & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no documentation contenthttps://lowpaymentfee.com/docs