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 26) 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 gated via the x402 protocol on the Base network and settled in USDC.
The specific endpoint `/api/v1/transactions/26/receipt` accepts POST requests and returns an `application/json` response. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). The platform advertises uniform $0.02/request pricing across all its endpoints with no API keys, no rate limits, and no minimum commitments.
The probe confirms the endpoint is live, returning a proper 402 challenge with x402 version 1. However, documentation is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the receipt resource actually contains or what input parameters the POST body expects. The platform appears to be a demonstration or early-stage deployment of x402-based pay-per-call APIs.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 26 via a single paid API call
- —Demonstrating x402 protocol-based pay-per-call API access on Base
- —Agent-driven programmatic access to receipt data without API key management
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Agents that need keyless, pay-per-call API access on Base
- —Use cases requiring low-cost ($0.02) per-request pricing with no commitments
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need detailed API documentation or SDKs
- —Bulk data retrieval where per-request costs would accumulate significantly
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/26/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment on Base to access.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no description of what the receipt resource contains or what POST body is expected. The listing is effectively a stub.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all render only 'Connect wallet'
- —No OpenAPI or request/response schema provided; input parameters for the POST body are unknown
- —The specific resource (transaction 26 receipt) is opaque — unclear what data it returns
- —Platform may be a demo or early-stage deployment; reliability and longevity are uncertain
Citations
- —The endpoint returns a 402 challenge with x402 version 1, maxAmountRequired 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/transactions/26/receipt
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/transactions/26/receipt
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs