Check order status via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns the status of order #23 (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 `/api/v1/orders/23/status` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers attach an X-PAYMENT header containing a signed USDC payment of up to 20,000 base units ($0.02, since USDC uses 6 decimals) to the payTo address on Base. No API keys, rate limits, or upfront commitments are required — each call is independently settled on-chain.
Documentation is extremely sparse. The provider's landing page lists many endpoints across categories but the docs, pricing, and API 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 endpoint is live (returns a valid 402 challenge), but the actual behavior and response format of the order-status call can only be guessed from the endpoint path and description.
Capabilities
Use cases
- —Checking the status of a specific order programmatically
- —Integrating order-status lookups into agent workflows that can pay per call
- —Demonstrating x402 protocol micropayments on Base
Fit
Best for
- —Agents or bots that need on-demand order status without managing API keys
- —Developers experimenting with x402 pay-per-request patterns
- —Low-volume, ad-hoc order status queries
Not for
- —High-volume order management systems needing bulk or subscription pricing
- —Users who need detailed API documentation or guaranteed SLAs
- —Querying orders beyond the fixed /orders/23/status path without knowing the URL pattern
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/23/status \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payment. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page listing, and the specific endpoint path (/orders/23/status) is a hardcoded order ID with no explanation of broader usage. Docs pages render only 'Connect wallet' with no content.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —All doc/pricing/API pages return only a 'Connect wallet' stub — no usable technical docs
- —The endpoint path references a specific order ID (23); it is unclear whether this generalizes to other order IDs
- —Response format and fields are completely undocumented
- —The provider lists many endpoints on the landing page but none have detailed documentation
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/orders/23/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 Base networkhttps://lowpaymentfee.com/api/v1/orders/23/status
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs