x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 133) 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 and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/133/receipt` accepts POST requests and returns `application/json`. Payment is made via the x402 exact scheme: the caller includes an `X-PAYMENT` header with a signed USDC payment on Base (contract `0x8335…2913`). The maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02 per call. No API keys or rate limits are advertised; access is granted purely through per-request micropayment.
Documentation 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 beyond the x402 challenge's `outputSchema` stub, and no explanation of what the receipt payload actually contains. The platform appears to be a demonstration or early-stage x402 showcase rather than a mature production API.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 133 via micropayment
- —Demonstrating x402 protocol payment flows on Base
- —Integrating pay-per-call USDC billing into agent workflows
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need to fetch transaction receipts without API keys
- —Testing USDC micropayment integrations on Base
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk or batch transaction receipt retrieval
- —Users without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/133/receipt \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-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 body schema, and no example responses. The docs/pricing/README pages are all empty wallet-connect stubs. The specific resource (transaction 133 receipt) is opaque with no explanation of what it returns.
Warnings
- —No OpenAPI or schema documentation available — request and response formats are unknown.
- —All documentation pages (docs, pricing, README, api) render only a 'Connect wallet' prompt with no content.
- —This appears to be a single hardcoded transaction ID (133); unclear if other transaction IDs are supported.
- —Platform may be a demo or early-stage project rather than a production service.
Citations
- —The endpoint returns a 402 challenge requiring USDC payment on Base network with maxAmountRequired of 20000 base units ($0.02).https://lowpaymentfee.com/api/v1/transactions/133/receipt
- —The platform advertises multiple API categories (Data & Analytics, AI & ML, Finance & Web3, Infrastructure) all at $0.02 per request.https://lowpaymentfee.com
- —The platform claims no API keys, no rate limits, and instant access with Base network settlement.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/transactions/133/receipt