Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" receipt for transaction ID 160. It is part of a broader platform offering dozens of pay-per-call 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/160/receipt` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring a maximum of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call, paid to address `0x1A2B...85F3` on Base. No API keys or rate limits are advertised; access is gated purely by the x402 micropayment protocol.
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 schema, no request/response examples, and no description of what the receipt payload actually contains. The platform's landing page lists many other endpoints (sentiment analysis, summarization, geocoding, gas estimates, etc.) at the same $0.02 price point, but without documentation it is unclear what data or functionality each endpoint actually provides.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 160 via micropayment
- —Demonstrating x402 protocol integration for pay-per-call APIs
- —Agent-driven programmatic access to paid endpoints without API key management
Fit
Best for
- —Developers experimenting with x402 micropayment protocol
- —Agents needing keyless, pay-per-use API access on Base
- —Projects requiring USDC-settled per-call billing
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need free or subscription-based API access
- —Applications needing high-throughput batch processing (no documented rate limits but no guarantees either)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/160/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the receipt contains. The docs pages are all empty wallet-connect prompts. This is effectively a stub listing.
Warnings
- —No documentation available — all doc/API/pricing/README pages render only 'Connect wallet' with no content
- —No OpenAPI or JSON schema describing request parameters or response format
- —Unknown what data the transaction receipt actually returns
- —The endpoint is for a specific transaction ID (160); unclear if other transaction IDs are supported or how they are discovered
- —Platform lists many endpoints but none have documented behavior
Citations
- —Endpoint returns 402 with x402 challenge requiring 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/160/receipt
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/160/receipt
- —All APIs priced at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Platform offers endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com