Check order status via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns the status of order #193 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 across data analytics, AI/ML inference, finance/Web3, and infrastructure utility categories — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/193/status` is labeled "Premium API Access" in the x402 challenge. The payment scheme is "exact" with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. No API keys or rate limits are advertised; callers pay per request using the x402 protocol's X-PAYMENT header. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds.
Note that this specific endpoint appears to be for a single hardcoded order ID (193), so its general utility is unclear. The broader platform lists many other endpoints (analytics, AI, finance, utilities) at the same price point, but those are separate resources. Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available.
Capabilities
Use cases
- —Checking the status of a specific order via programmatic micropayment
- —Demonstrating x402 protocol payment flows on Base network
- —Agent-driven order tracking with per-call USDC settlement
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call order status checks without API keys
- —Prototyping micropayment-gated API access on Base
Not for
- —Production order management systems requiring arbitrary order IDs
- —Users needing detailed API documentation or OpenAPI specs
- —High-volume batch order status queries (no documented bulk endpoint)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/193/status \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no request/response schema, no examples, and the endpoint is hardcoded to a single order ID (193) with unclear general utility. Docs pages are empty beyond a wallet connect prompt.
Warnings
- —Endpoint is hardcoded to order ID 193 — unclear if other order IDs are supported or how to discover them
- —No OpenAPI spec, no request/response schema, and no documentation beyond the landing page
- —All docs/pricing/API/README pages render only 'Connect wallet' with no actual content
- —The 'Premium API Access' label is generic and does not describe what data is returned
Citations
- —The x402 challenge requires 20,000 base units of USDC on Base, equaling $0.02 per requesthttps://lowpaymentfee.com/api/v1/orders/193/status
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/orders/193/status
- —Docs, API, pricing, and README pages all show only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs