Transaction receipt retrieval via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (transaction ID 155) behind an x402 paywall. It is part of a broader platform offering dozens of pay-per-call API endpoints 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/155/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The x402 challenge advertises a max amount of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. No API keys, rate limits, or subscriptions are required — each call is independently paid.
Documentation on the site 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 examples available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual shape of the receipt response and what input the POST body expects are unknown.
Capabilities
Use cases
- —Retrieving a receipt for a specific transaction (ID 155) via programmatic API call
- —Demonstrating x402 protocol integration for pay-per-call services
- —Agent-driven receipt fetching without pre-registration or API keys
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents needing on-demand transaction receipt data without subscriptions
- —Low-friction, no-signup API access paid in USDC on Base
Not for
- —Bulk retrieval of many different transaction receipts (only transaction 155 is exposed at this URL)
- —Users who need detailed API documentation or request/response schemas before integrating
- —Non-crypto users who cannot pay in USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/155/receipt \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but documentation is essentially nonexistent — docs/pricing/API pages all show only 'Connect wallet'. No OpenAPI spec, no request/response schemas, no examples. The endpoint path is specific to a single transaction ID (155), making its general utility unclear.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all render only 'Connect wallet'
- —No OpenAPI or schema definition; request body format and response structure are unknown
- —Endpoint is scoped to a single transaction ID (155); unclear if other transaction IDs are available at similar paths
- —The broader platform advertises many endpoints (AI, analytics, finance, utils) but none have documented schemas
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/transactions/155/receipt
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/155/receipt
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs