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 190. 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/190/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 content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples. The exact purpose of the "transaction receipt" resource (whether it returns a receipt for a prior payment, or serves some other function) is unclear from available materials. The broader platform lists many endpoints but provides no detailed documentation for any of them.
Capabilities
Use cases
- —Retrieving a transaction receipt via micropayment on Base
- —Programmatic pay-per-call access without API keys
- —Agent-driven USDC micropayment workflows on Base L2
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents needing keyless, pay-per-call API access on Base
- —Users who want to avoid subscription commitments for occasional API calls
Not for
- —Production workloads requiring detailed API documentation and SLAs
- —Users who need non-crypto payment methods
- —High-volume use cases where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/190/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. However, documentation is essentially nonexistent beyond the landing page — /docs, /pricing, /api, and /README all show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what this specific receipt endpoint actually returns. The purpose of 'transaction 190 receipt' is opaque.
Warnings
- —No API documentation available — all doc pages render only 'Connect wallet'
- —No OpenAPI or JSON schema describing request parameters or response format
- —The specific purpose of the /transactions/190/receipt endpoint is unclear
- —The broader platform lists many endpoints but none have documented schemas or examples
- —Cannot verify what data the endpoint actually returns without paying
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/190/receipt
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/190/receipt
- —Platform advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —Platform lists endpoints for analytics, AI/ML, finance, and infrastructure categorieshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) show only 'Connect wallet'https://lowpaymentfee.com/docs