Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" transaction receipt resource at `/api/v1/transactions/255/receipt`. It is part of a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The endpoint accepts POST requests and returns `application/json` responses. 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) to the payee address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The payment scheme is "exact" with a 300-second timeout. No API keys or rate limits are advertised; access is instant once payment is provided.
The specific endpoint probed (`/transactions/255/receipt`) appears to return a receipt for transaction ID 255. The broader platform lists endpoints for metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. Documentation pages (`/docs`, `/pricing`, `/api`, `/README`) returned only a "Connect wallet" prompt with no substantive content, so the actual request/response schemas for this and other endpoints remain undocumented.
Capabilities
Use cases
- —Retrieving a transaction receipt for a specific transaction ID via micropayment
- —Programmatic access to paid API resources without API key management
- —Agent-driven workflows that need on-chain payment settlement per call
Fit
Best for
- —Developers wanting keyless, pay-per-call API access settled in USDC on Base
- —AI agents that can autonomously pay for API calls via x402
- —Users who prefer no subscriptions or rate limits
Not for
- —Users needing detailed API documentation or response schema guarantees before integrating
- —High-volume batch processing where per-call pricing may add up
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/255/receipt \
-H "X-PAYMENT: <x402-signed-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). However, there is no OpenAPI schema, no documented request/response format, no examples, and all documentation pages return only a wallet-connect prompt. The specific purpose of this receipt endpoint is only inferable from the URL path.
Warnings
- —No API documentation available — all doc pages (/docs, /pricing, /api, /README) return only 'Connect wallet' with no content
- —No request or response schema provided for this or any endpoint on the platform
- —The specific behavior of /api/v1/transactions/255/receipt is undocumented; the resource path suggests a receipt for transaction 255 but this is inferred
- —The broader platform advertises many endpoints (AI, finance, utilities) but none have documented schemas
Citations
- —The endpoint returns a 402 challenge requiring USDC payment of 20,000 base units ($0.02) on Base networkhttps://lowpaymentfee.com/api/v1/transactions/255/receipt
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/255/receipt
- —Documentation pages (/docs, /pricing, /api, /README) contain only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs