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 64. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/64/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 payment protocol.
Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's `outputSchema`, and no examples of what the receipt payload actually contains. The platform lists many other endpoints (sentiment analysis, summarization, embeddings, price feeds, geocoding, etc.) at the same $0.02 price point, but none have documented schemas either. Treat this as a low-documentation, exploratory-stage service.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 64 via a single paid API call
- —Demonstrating x402 payment-gated API access patterns on Base
- —Integrating pay-per-use API calls into agent workflows without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents needing keyless, pay-per-call API access on Base
- —Prototyping micropayment-gated service architectures
Not for
- —Production workloads requiring well-documented, schema-validated APIs
- —Bulk transaction receipt retrieval (single transaction ID hardcoded in path)
- —Users who need fiat-only payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/64/receipt \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no examples, and the docs pages render only a wallet-connect prompt. The specific endpoint serves a single hardcoded transaction ID with unknown response structure.
Warnings
- —No OpenAPI spec or request/response schema available
- —Docs, pricing, and API pages all render only 'Connect wallet' with no technical content
- —Endpoint path contains a hardcoded transaction ID (64) — unclear if other IDs are supported
- —The platform lists many endpoints but none have documented behavior or schemas
- —Response payload structure is completely unknown
Citations
- —The endpoint returns a 402 challenge requiring 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/64/receipt
- —All APIs on the platform are priced at $0.02 per request with no API keys or rate limitshttps://lowpaymentfee.com
- —The platform offers endpoints across data analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/transactions/64/receipt