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 #101 (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, settled in USDC on the Base network.
The specific endpoint probed (`/api/v1/orders/101/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) to the specified payTo address on Base. No API keys, rate limits, or upfront commitments are required — access is instant once payment is verified.
Documentation is extremely thin. The landing page lists available API categories and a uniform $0.02 price, but the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples. The actual behavior and response format of the order-status endpoint must be inferred entirely from the endpoint path and the x402 challenge metadata.
Capabilities
Use cases
- —Checking the status of an order programmatically via a single micropayment
- —Integrating order-status lookups into an agent workflow without managing API keys
- —Demonstrating x402 payment-gated API access on Base
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need keyless, pay-per-call API access
- —Quick one-off order status checks without subscription overhead
Not for
- —High-volume order management systems needing bulk queries at lower marginal cost
- —Users who need detailed API documentation or guaranteed SLAs
- —Applications requiring order creation or mutation, not just status reads
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/101/status \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The specific purpose of this endpoint (order status for order 101) is narrow and undocumented. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown.
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content.
- —The endpoint path is hardcoded to order 101; it is unclear whether other order IDs are supported or what the broader order system entails.
- —The 'Premium API Access' description is generic and does not describe the actual functionality.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/orders/101/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 asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/orders/101/status