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 #192 via a POST request, gated behind 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, payable in USDC on the Base network with no API keys, rate limits, or commitments required.
The specific endpoint `/api/v1/orders/192/status` is labeled "Premium API Access" in the x402 challenge. The payment is settled on-chain using the exact-amount scheme: 20,000 base units of USDC (6 decimals) = $0.02. The platform advertises a uniform $0.02/request pricing across all its endpoints. Payment is made via the X-PAYMENT header per the x402 protocol (version 1), with a 300-second timeout.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all resolve to a minimal "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no example payloads. The endpoint is live (returns 402 as expected for x402), but the actual response body after successful payment is unknown.
Capabilities
Use cases
- —Checking the status of a specific order programmatically with per-call USDC payment
- —Integrating x402-compatible agents that pay for API access on the Base network
- —Demonstrating x402 protocol micropayment flows for order management
Fit
Best for
- —Agents or apps that already support x402 payment protocol
- —Users who want keyless, pay-per-request API access on Base
- —Developers experimenting with crypto-micropayment-gated endpoints
Not for
- —Users needing bulk order status checks (no batch endpoint documented)
- —Anyone without a Base-network USDC wallet
- —Production use cases requiring documented request/response schemas
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/192/status
# Returns 402 with x402 challenge. Include X-PAYMENT header with valid payment proof to receive the order status response.Endpoint
Quality
The endpoint is live (402 challenge captured), pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no documented request body, no example response, and the docs pages are all empty stubs. The endpoint path is hardcoded to a single order ID (192), making its general utility unclear.
Warnings
- —Documentation pages (/docs, /pricing, /api, /README) are all empty — only a 'Connect wallet' prompt is rendered.
- —No OpenAPI or request/response schema available; actual response payload after payment is unknown.
- —Endpoint path is hardcoded to order 192 — unclear if this generalizes to other order IDs.
- —The platform lists many other endpoints (AI, finance, utils) but this listing covers only /api/v1/orders/192/status.
Citations
- —Uniform pricing of $0.02 per request across all endpoints, no API keys, no rate limitshttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (USD Coin) on Base network with 300s timeouthttps://lowpaymentfee.com/api/v1/orders/192/status
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/orders/192/status