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 #142 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/142/status` appears to be an order-status lookup. The x402 challenge confirms it is live, accepting USDC (contract 0x8335…2913 on Base) with a maxAmountRequired of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). Payment is made via the x402 `exact` scheme with a 300-second timeout. No API keys or rate limits are advertised; access is granted per-request upon payment.
Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI spec, no request/response schema, and no usage examples. The platform's landing page lists many endpoints across categories but provides no detail on request parameters or response formats. As a result, the actual behavior of this specific endpoint (what fields it returns, what input it expects) must be treated as unknown.
Capabilities
Use cases
- —Checking the status of a specific order (#142) programmatically
- —Demonstrating x402 payment-gated API access on Base
- —Agent-driven order tracking with per-call USDC micropayments
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call order status without API key management
- —Low-friction one-off API calls settled in USDC on Base
Not for
- —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 142)
- —Users who need detailed API documentation or response schemas before integrating
- —Non-crypto users who cannot pay in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/142/status \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a landing page listing, no request/response schema, and the endpoint is hardcoded to a single order ID, making its general utility unclear.
Warnings
- —No OpenAPI spec or response schema available — actual response format is unknown
- —Endpoint is hardcoded to order ID 142; unclear if other order IDs are supported via different URLs
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —The platform lists many endpoints but provides zero detail on any of them
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/orders/142/status
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/142/status