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 resource for transaction ID 299. It is part of a broader platform offering dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all settled on the Base network using USDC at $0.02 per request via the x402 protocol.
The specific endpoint `/api/v1/transactions/299/receipt` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring an exact payment of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) to wallet 0x1A2B…85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is gated purely by micropayment.
Documentation beyond the landing page is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available from the crawl. The exact purpose of a "transaction receipt" endpoint is unclear — it may return a receipt or proof-of-payment for a prior transaction, but this is speculative given the lack of documentation.
Capabilities
Use cases
- —Retrieving a receipt or proof-of-payment for a specific transaction
- —Agent-driven micropayment workflows that need on-chain settlement
- —Programmatic access to transaction data without API key management
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need keyless, pay-per-call API access on Base
- —Use cases requiring USDC-settled API calls with no subscription
Not for
- —Production workloads requiring documented request/response schemas
- —Bulk or high-volume data retrieval where per-call pricing is inefficient
- —Users who need fiat payment rails or non-crypto settlement
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/299/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but documentation is essentially nonexistent — all subpages render only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the purpose of this specific receipt endpoint is unclear. The listing is effectively a stub.
Warnings
- —No documentation available beyond the landing page; /docs, /pricing, /api, /README all show only 'Connect wallet'
- —No OpenAPI or schema definition found for request or response payloads
- —The specific purpose of /api/v1/transactions/299/receipt is unclear — it may be a demo or placeholder endpoint
- —No examples of successful responses are available
Citations
- —The endpoint returns a 402 challenge requiring 20,000 base units of USDC on Base (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)https://lowpaymentfee.com/api/v1/transactions/299/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —Available API categories include Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com