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 (resource path `/api/v1/transactions/319/receipt`) behind an x402 paywall. It is part of a broader platform offering numerous pay-per-call API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utility categories — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 exact scheme with no API keys or rate limits required. The response MIME type is `application/json`. The endpoint accepts POST requests and is discoverable.
Documentation on the site is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The platform's landing page lists many endpoints but provides no detail on request parameters or response formats for any of them, including this receipt endpoint. The actual content and structure of the receipt response is unknown.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 319 via programmatic micropayment
- —Demonstrating x402 protocol payment flow on Base network
- —Integrating pay-per-call receipt retrieval into agent workflows
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents needing on-demand transaction receipt data without API key management
- —Low-volume, pay-as-you-go receipt lookups
Not for
- —High-volume batch receipt retrieval (no documented bulk endpoints)
- —Users needing detailed API documentation or response schema guarantees before integration
- —Non-crypto payment workflows (only USDC on Base is accepted)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/319/receipt \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no OpenAPI spec, no documented request/response schema, no usage examples, and the docs pages are empty beyond a wallet connect prompt. The purpose of this specific receipt endpoint (transaction 319) is unclear — it may be a demo or a fixed resource. Very little can be inferred about what the response contains.
Warnings
- —No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
- —No request or response schema is documented for this or any endpoint on the platform.
- —The endpoint path references a specific transaction ID (319); it is unclear whether this is a generic pattern or a single fixed resource.
- —The platform lists many endpoint categories (AI, analytics, finance, etc.) but provides zero detail on any of them beyond names and price.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/transactions/319/receipt
- —All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/319/receipt
- —Docs, API, pricing, and README pages render only a 'Connect wallet' prompt with no further contenthttps://lowpaymentfee.com/docs