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 #170 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/170/status` is listed under the title "Premium API Access" but appears to be an order-status lookup. The x402 challenge confirms the endpoint is live, accepting USDC (contract 0x8335…2913 on Base) with a max amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). Payment is made via the x402 `exact` scheme with a 300-second timeout. No API keys or rate limits are required; access is instant once payment is included in the X-PAYMENT header.
Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no examples of what the order-status response looks like. The platform advertises many other endpoints across analytics, AI, finance, and utility categories, all at the same $0.02 price point, but specifics on request parameters and response formats are unavailable.
Capabilities
Use cases
- —Checking the status of a specific order programmatically with per-call payment
- —Demonstrating x402 payment protocol integration on Base network
- —Agent-driven order tracking without pre-provisioned API keys
Fit
Best for
- —Developers experimenting with x402 micropayment protocol
- —Agents needing keyless, pay-per-use order status checks
- —Low-volume order status lookups without subscription commitments
Not for
- —High-volume order management systems needing bulk status queries
- —Users who need detailed order-status response schemas before integrating
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/170/status \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/orders/170/status",
"method": "POST",
"headers": {
"X-PAYMENT": "<x402-payment-token>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI spec, no response schema, and no examples of what the endpoint actually returns. The docs/pricing/README pages are all blank beyond a wallet-connect prompt. The endpoint path is hardcoded to order 170, making its general utility unclear.
Warnings
- —No OpenAPI or response schema available — response format is entirely unknown
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —Endpoint path is hardcoded to order ID 170; unclear if other order IDs are supported or how to discover them
- —Platform advertises many endpoints but none have documented request/response contracts
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/orders/170/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 contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/170/status