Pay-per-call transaction receipt endpoint on Base via x402, priced at $0.02 in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" receipt for transaction 302. It is part of a broader platform offering dozens of pay-per-request 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/302/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers attach an X-PAYMENT header containing a signed USDC payment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base mainnet using the USDC contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The endpoint was confirmed live, returning a proper 402 challenge.
Documentation beyond the landing page is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The exact purpose of a "transaction 302 receipt" is unclear; it may be a demo or placeholder endpoint. The platform advertises no API keys, no rate limits, and instant access, but these claims cannot be independently verified from the crawled material.
Capabilities
Use cases
- —Retrieving a transaction receipt via a single micropayment without API key registration
- —Demonstrating x402 protocol payment flows on Base mainnet
- —Integrating pay-per-use API calls into agent workflows that settle in USDC
Fit
Best for
- —Developers experimenting with x402 payment protocol integration
- —Agents needing keyless, pay-per-call API access on Base
- —Projects requiring USDC-settled micropayment endpoints
Not for
- —Production workloads requiring documented request/response schemas
- —Use cases needing free or subscription-based API access
- —Applications requiring detailed transaction data beyond a receipt
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/302/receipt \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but documentation is essentially nonexistent — no OpenAPI spec, no request/response examples, and no explanation of what the receipt endpoint actually returns. The purpose of 'transaction 302' is unexplained. Score reflects a functional but poorly documented stub.
Warnings
- —No OpenAPI or schema documentation available; /docs, /api, /pricing, /README all return only a wallet-connect prompt
- —The specific purpose and response format of /api/v1/transactions/302/receipt is undocumented
- —Claims of 'no rate limits' and 'no API keys' cannot be verified from available material
- —The endpoint path includes a hardcoded transaction ID (302), suggesting it may be a demo or placeholder
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/302/receipt
- —The platform lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categories all priced at $0.02 per requesthttps://lowpaymentfee.com
- —The platform advertises no API keys, no rate limits, instant access, and Base network settlementhttps://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and payTo is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/transactions/302/receipt