x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (transaction ID 387) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/387/receipt` accepts POST requests and returns an `application/json` response. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The x402 challenge advertises a `maxAmountRequired` of 20,000 base units of USDC (contract `0x8335…2913` on Base), which equals $0.02 given USDC's 6 decimal places. The payment scheme is "exact" with a 300-second timeout.
The platform advertises no API keys, no rate limits, and instant access. Documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all returned only a "Connect wallet" prompt with no substantive content, so the actual response schema, request parameters, and detailed behavior of this endpoint are unknown. The broader site lists many endpoints but provides no OpenAPI spec or detailed documentation for any of them.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 387 via a single paid API call
- —Demonstrating x402 protocol payment flows for agent-to-agent commerce
- —Integrating pay-per-request data access without API key management
Fit
Best for
- —Agents or developers experimenting with x402 payment protocol
- —Use cases requiring keyless, pay-per-call API access on Base
- —Scenarios where low per-request cost ($0.02) is important
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based access rather than per-call crypto payments
- —Bulk data retrieval where per-request fees would accumulate significantly
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/387/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a wallet-connect prompt, no request/response schema, and the specific purpose of 'transaction 387 receipt' is unexplained. This is effectively a stub listing.
Warnings
- —No OpenAPI spec or machine-readable schema available
- —All documentation pages (/docs, /pricing, /api, /README) returned only 'Connect wallet' with no content
- —The specific endpoint path references a hardcoded transaction ID (387) — unclear if this is a demo or a real resource
- —Request body schema and response schema are completely unknown
- —No information on what data the receipt actually contains
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base with scheme 'exact' and 300-second timeouthttps://lowpaymentfee.com/api/v1/transactions/387/receipt
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/387/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access, Base networkhttps://lowpaymentfee.com
- —Documentation pages returned only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs