Check order status via x402 micropayment on Base (USDC, $0.02/request).
What it does
This endpoint at lowpaymentfee.com returns the status of order #125 via a POST request, gated by an x402 payment challenge. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/125/status` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, 6 decimals), which equals $0.02. Payment is made via the x402 exact scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a timeout of 300 seconds. No API keys or rate limits are advertised; access is instant upon payment.
Documentation is extremely thin — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the order status response actually contains. The endpoint path is hardcoded to order 125, so it is unclear whether this is a demo/sample endpoint or whether other order IDs are supported via similar paths.
Capabilities
Use cases
- —Checking the status of a specific order via a single paid API call
- —Demonstrating x402 micropayment integration on the Base network
- —Agent-driven order tracking workflows that settle per-request in USDC
Fit
Best for
- —Developers exploring x402 payment-gated APIs
- —Agents needing pay-per-call order status lookups without API keys
- —Testing micropayment flows on Base with USDC
Not for
- —Bulk order management or batch status queries
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Production order tracking systems requiring parameterized order IDs (only order 125 is documented)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/125/status \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, no meaningful documentation, and the endpoint path is hardcoded to a single order ID. Almost everything beyond the challenge itself must be inferred.
Warnings
- —No OpenAPI or schema documentation available — docs pages render only 'Connect wallet'
- —Endpoint path is hardcoded to order 125; unclear if other order IDs are supported
- —No request body schema or response schema provided
- —No examples of successful responses available
- —The 'Premium API Access' label is generic and does not describe what data is returned
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/orders/125/status
- —All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform offers APIs across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com