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 #197 via a POST request, gated by an x402 payment challenge. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs — all priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/197/status` accepts POST requests and requires an X-PAYMENT header containing a valid x402 payment proof. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
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 request/response payloads, and no description of what the order status response actually contains. The endpoint path is hardcoded to order 197, so it is unclear whether this is a demo/example or a production resource. The broader site lists many other endpoints across analytics, AI, finance, and utility categories, all at the same $0.02 price point.
Capabilities
Use cases
- —Checking the status of a specific order via a single paid API call
- —Demonstrating x402 payment flow integration on Base
- —Agent-driven order tracking with per-request USDC micropayments
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to query order status with no API key setup
- —Micropayment-gated API access without subscriptions
Not for
- —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 197)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Production order tracking systems requiring guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/197/status \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documentation beyond a wallet-connect prompt, no example request/response, and the endpoint is hardcoded to a single order ID with no explanation of what it returns. This is effectively a stub listing.
Warnings
- —Documentation pages (/docs, /pricing, /README) all return only a 'Connect wallet' prompt with no actual content.
- —Endpoint is hardcoded to order ID 197 — unclear if this is a demo or a real resource.
- —No OpenAPI spec, no example responses, and no description of the response schema.
- —No information about what 'order status' actually returns or what data model it follows.
- —The broader platform lists many endpoints but none have documented schemas.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base with a 300-second timeout.https://lowpaymentfee.com/api/v1/orders/197/status
- —All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access.https://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base network.https://lowpaymentfee.com/api/v1/orders/197/status