x402-gated transaction receipt endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 204) behind an x402 paywall. It is part of a broader platform that advertises multiple API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/204/receipt` accepts POST requests and returns `application/json`. Payment is made via the x402 exact-payment scheme: the caller attaches an X-PAYMENT header containing a signed USDC transfer on Base. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02 per call. The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a timeout of 300 seconds.
The platform markets itself as requiring no API keys, no rate limits, and no commitments — just per-request micropayments. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all returned only a "Connect wallet" prompt with no substantive content, so the actual response schema, request parameters, and detailed behavior of this endpoint are unknown. The broader site lists many endpoints across categories but provides no OpenAPI spec or detailed docs for any of them.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 204 via a single micropayment
- —Demonstrating x402 payment flows for agent-to-API commerce
- —Integrating pay-per-call receipt retrieval into automated workflows
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need on-demand transaction receipts without API key management
- —Low-volume, pay-as-you-go access to receipt data
Not for
- —High-volume batch retrieval where per-request fees add up
- —Users who need detailed API documentation or response schema guarantees before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/204/receipt
# Returns 402 with x402 challenge. Attach a signed USDC payment in the X-PAYMENT header to access.Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI spec, no response schema, and no example responses. All doc pages return only a wallet-connect prompt. The purpose of this specific receipt endpoint is unclear beyond its URL path.
Warnings
- —No documentation available — all doc/pricing/README pages return only 'Connect wallet' with no content.
- —No OpenAPI or output schema provided; the actual response format is unknown.
- —The endpoint path references a specific transaction ID (204); it is unclear whether this is a generic pattern or a single fixed resource.
- —The broader platform lists many endpoints but none have verifiable documentation or examples.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/204/receipt
- —maxAmountRequired is 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02https://lowpaymentfee.com/api/v1/transactions/204/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) contain only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs