Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/124/receipt`. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced uniformly at $0.02 per request with no API keys, no rate limits, and no commitments required.
The specific endpoint probed returns a 402 Payment Required challenge requesting payment of 20,000 base units of USDC (0x8335…2913) on the Base network, which equals $0.02 USD (USDC uses 6 decimals). Payment is made via the x402 exact scheme, with a 300-second timeout. The response MIME type is `application/json`. The endpoint accepts POST requests and is marked as discoverable.
The platform's landing page lists 16 endpoints across four categories, all at the same $0.02 price point. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation available for any endpoint. The actual data or functionality behind this particular receipt endpoint is unclear — the description simply says "Premium API Access" with no further detail on what the receipt contains or what inputs it expects.
Capabilities
Use cases
- —Retrieving a transaction receipt for transaction ID 124 via a single paid API call
- —Demonstrating x402 payment flow integration with USDC on Base
- —Agent-driven pay-per-use API consumption without pre-registration
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents needing keyless, pay-per-call API access on Base
- —Projects requiring low-cost micropayment-gated endpoints
Not for
- —Production workloads requiring documented request/response schemas
- —Users who need detailed API documentation or SDKs
- —Bulk data retrieval where per-call pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/transactions/124/receipt
# Returns 402 with x402 payment challenge.
# Include X-PAYMENT header with valid payment proof to receive the receipt.Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs showing only 'Connect wallet'. The purpose of this specific receipt endpoint is unclear beyond its generic 'Premium API Access' label.
Warnings
- —All documentation pages (/docs, /pricing, /api, /README) return no useful content — only a 'Connect wallet' prompt.
- —No OpenAPI or schema definition is available for any endpoint on the platform.
- —The specific resource at /api/v1/transactions/124/receipt has no documented input parameters or response format.
- —It is unclear whether the hardcoded transaction ID '124' is meaningful or if this is a demo/placeholder endpoint.
- —The platform lists 16 endpoints but none have detailed documentation; actual functionality is unverified.
Citations
- —The endpoint returns a 402 challenge requesting 20,000 base units of USDC on Base network with a 300-second timeouthttps://lowpaymentfee.com/api/v1/transactions/124/receipt
- —The platform lists 16 endpoints across four categories all priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/transactions/124/receipt
- —Documentation pages return only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs