Transaction receipt retrieval via x402 micropayment on Base network, $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource path `/api/v1/transactions/313/receipt`) behind an x402 paywall. Payment is settled on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) at a cost of $0.02 per request (20,000 base units with 6 decimals). The endpoint accepts POST requests and returns `application/json`.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments — payment is handled entirely through the x402 protocol.
Documentation 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 from the crawled material. The specific purpose of the `/transactions/313/receipt` endpoint — whether it retrieves a blockchain transaction receipt, a payment receipt, or something else — is not documented. Prospective users should be aware that they are paying before knowing the exact response structure.
Capabilities
Use cases
- —Retrieving a transaction receipt programmatically via micropayment
- —Integrating pay-per-call receipt lookups into agent workflows
- —Demonstrating x402 protocol payment flows on Base
Fit
Best for
- —Developers experimenting with x402 protocol integrations
- —Agents needing on-demand transaction receipt data without API key management
- —Low-volume, pay-as-you-go receipt retrieval
Not for
- —High-volume batch receipt processing where per-call fees add up
- —Users who need detailed API documentation or response schema guarantees before paying
- —Applications requiring non-USDC or non-Base-network payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/313/receipt \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payment. However, documentation is effectively nonexistent — every doc/pricing/API page returns only 'Connect wallet'. There is no OpenAPI spec, no request/response examples, and the specific purpose of this particular receipt endpoint is unclear. The listing is largely a stub.
Warnings
- —No API documentation available; docs, pricing, API, and README pages all show only 'Connect wallet'
- —No request or response schema documented — callers pay before knowing what they receive
- —The specific semantics of /api/v1/transactions/313/receipt (what transaction 313 refers to) are undocumented
- —No OpenAPI or ai-plugin manifest found
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/transactions/313/receipt
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/transactions/313/receipt
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/313/receipt
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs