Transaction receipt endpoint on Base, paid per-call via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt for transaction ID 151, accessible via the x402 payment protocol. 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/151/receipt` returns a JSON response upon a POST request with a valid x402 payment header. The x402 challenge confirms the endpoint is live, accepting USDC (contract 0x8335…2913 on Base) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The platform emphasizes simplicity: no API keys, no rate limits, no commitments — just pay-per-request via crypto.
Documentation is extremely sparse. The docs, API, pricing, 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 a "transaction receipt" contains or what input parameters the POST body expects. The platform lists many other endpoints on its landing page, but this listing covers only the `/api/v1/transactions/151/receipt` resource.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction (ID 151) via programmatic payment
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agent-driven workflows that need verifiable transaction receipts
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to fetch transaction receipts without API key management
- —Low-cost per-call access to receipt data
Not for
- —Bulk retrieval of many transaction receipts (only one transaction ID exposed)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Non-crypto payment workflows — requires USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/151/receipt \
-H "X-PAYMENT: <x402_payment_header>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing and payment details, but documentation is essentially nonexistent — every doc page returns only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what the endpoint actually returns. The endpoint path is hardcoded to a single transaction ID (151), which limits general usefulness.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) contain no substantive content — only 'Connect wallet' prompts.
- —No OpenAPI or schema available; request body format and response structure are unknown.
- —Endpoint is scoped to a single hardcoded transaction ID (151); unclear if other transaction IDs are available.
- —The platform lists many other endpoints on its landing page, but none were probed — their availability is unverified.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/transactions/151/receipt
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/transactions/151/receipt
- —Documentation, API, pricing, and README pages render only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs