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 #111 via a POST request, gated by the x402 payment protocol. It is part of a broader platform that offers 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/111/status` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (the asset at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base, which has 6 decimals), equating to $0.02 per call. Payment is made via the x402 "exact" scheme: callers attach an X-PAYMENT header with a signed payment to the payTo address. No API keys, rate limits, or subscriptions are required — each request is individually settled on-chain.
Documentation on the site is extremely sparse. 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 explanation of what the order status response actually contains. The endpoint path suggests it returns status information for a specific order (ID 111), but whether this is a demo/sample order or a parameterized route is unclear. The broader platform lists many other endpoints (analytics, AI, finance, utilities) at the same $0.02 price point, but none have documented schemas either.
Capabilities
Use cases
- —Checking the status of an order via a single paid API call
- —Demonstrating x402 micropayment integration on Base
- —Agent-driven order tracking with per-request USDC settlement
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need to make one-off paid API calls without API keys
- —Testing micropayment flows on Base network
Not for
- —Production order management systems (no documented schema or SLA)
- —Users who need detailed API documentation before integrating
- —High-volume order tracking where per-request fees add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/111/status \
-H "X-PAYMENT: <x402-signed-payment>" \
-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 the purpose of this specific endpoint (order 111 status) is ambiguous. Effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
- —No request or response schema provided; unknown what the endpoint actually returns
- —Endpoint path is hardcoded to order ID 111 — unclear if this is parameterizable or a demo
- —No OpenAPI or ai-plugin manifest discovered
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/orders/111/status
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base (6 decimals), so 20000 base units = $0.02https://lowpaymentfee.com/api/v1/orders/111/status
- —Platform lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categories all at $0.02 per requesthttps://lowpaymentfee.com
- —Platform advertises no API keys, no rate limits, instant access, Base networkhttps://lowpaymentfee.com