Check order status via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns the status of order #50 (and presumably other orders at similar paths) behind an x402 paywall. The provider operates a broad suite of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint probed — `/api/v1/orders/50/status` — is labeled "Premium API Access" in the x402 challenge. It accepts POST requests and returns JSON. Payment is handled via the x402 exact-payment scheme: the caller includes an X-PAYMENT header with a USDC payment of up to 20,000 base units (i.e., $0.02 given USDC's 6 decimals) to the specified payTo address on Base. No API keys or rate limits are advertised; access is gated purely by micropayment.
Documentation is extremely thin. The /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no explanation of what fields the order status response contains. The provider's landing page confirms the $0.02 pricing and lists many other endpoints, but provides no detailed documentation for any of them.
Capabilities
Use cases
- —Checking the status of a specific order via a single micropayment
- —Integrating order-status lookups into an agent workflow without managing API keys
- —Programmatic order tracking settled on-chain via USDC on Base
Fit
Best for
- —Agents that need simple, keyless order-status queries
- —Developers experimenting with x402 micropayment protocols
- —Workflows where per-call payment is preferred over subscriptions
Not for
- —Bulk order management or batch status queries (no documented batch endpoint)
- —Users who need detailed API documentation or guaranteed SLAs
- —Non-crypto workflows that cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/50/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 spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the specific purpose of this 'orders/50/status' endpoint is unexplained. Effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README all return only a 'Connect wallet' prompt with no content.
- —No OpenAPI or request/response schema provided; response format is unknown.
- —The endpoint path '/api/v1/orders/50/status' has a hardcoded order ID (50); it is unclear whether this generalizes to other order IDs or what 'orders' refers to in this context.
- —Provider lists many endpoints on its landing page but none have documented behavior.
Citations
- —The x402 challenge requires up to 20,000 base units of USDC (asset 0x8335…) on Base, equaling $0.02.https://lowpaymentfee.com/api/v1/orders/50/status
- —The provider advertises $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) render only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs