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 serves a transaction receipt for transaction ID 328. It is part of a broader platform offering pay-per-request APIs across data analytics, AI/ML inference, finance/Web3, and infrastructure utility categories — all priced uniformly at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/transactions/328/receipt` responds to GET requests and returns `application/json`. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The max amount required is 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), which equals $0.02 given USDC's 6 decimals. The payment timeout is 300 seconds.
The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (docs, pricing, README) all resolve to a minimal "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no example responses, and no detailed documentation for what the receipt payload contains or what the broader transaction context is. The endpoint is confirmed live (402 challenge captured), but the actual utility and data quality of the response remain unverifiable from available materials.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction 328 via a single paid API call
- —Demonstrating x402 protocol payment flows for agent-to-agent commerce
- —Integrating low-cost per-request APIs without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access without subscription overhead
- —Projects requiring USDC-settled micropayment API access on Base
Not for
- —Production systems needing well-documented, schema-validated APIs
- —Use cases requiring bulk or batch transaction receipt retrieval
- —Users who need fiat payment options or non-crypto settlement
Quick start
curl -X GET https://lowpaymentfee.com/api/v1/transactions/328/receipt \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI schema, no example responses, no meaningful documentation (all doc pages show only 'Connect wallet'), and the specific purpose of this receipt endpoint is unclear. The broader platform lists many endpoints but provides no detail on any of them.
Warnings
- —No documentation available — all doc/pricing/README pages resolve to a minimal 'Connect wallet' stub
- —No OpenAPI or output schema describing the receipt response payload
- —The endpoint is for a specific transaction ID (328); unclear if this is a demo or a real resource
- —No example responses available to verify data quality or structure
- —Platform lists many API categories (AI, finance, analytics) but none have verifiable documentation
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/328/receipt
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/transactions/328/receipt
- —Documentation pages resolve to minimal 'Connect wallet' content onlyhttps://lowpaymentfee.com/docs