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 (specifically for transaction ID 326) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs 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/326/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 accepted asset is USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The payment timeout is 300 seconds.
The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all resolve to a minimal "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation available. The actual data returned by this receipt endpoint is unknown — it could be a transaction receipt, a proof of payment, or similar. The broader platform lists many endpoints but their actual functionality and data quality cannot be verified from available materials.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 326 via a single micropayment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base
- —Use cases requiring keyless, pay-per-call API access
Not for
- —Production workloads requiring documented schemas and SLAs
- —Users who need non-crypto payment methods
- —Bulk retrieval of multiple transaction receipts (endpoint is scoped to a single transaction ID)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/326/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no meaningful documentation (all doc pages show only 'Connect wallet'), and the actual data returned is completely unknown. The endpoint is scoped to a single hardcoded transaction ID (326), which limits general utility.
Warnings
- —No documentation available — all doc pages (/docs, /pricing, /api, /README) render only a 'Connect wallet' prompt with no content
- —No OpenAPI or schema describing request parameters or response format
- —Endpoint is scoped to a single transaction ID (326); unclear if this is a demo or production resource
- —Actual response payload is unknown — cannot verify what data is returned
- —Broader platform lists many endpoints but none have verifiable documentation or examples
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/326/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/326/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Documentation pages resolve to minimal 'Connect wallet' content onlyhttps://lowpaymentfee.com/docs