Check order status via x402 micropayment on Base (USDC, $0.02/request).
What it does
This endpoint at lowpaymentfee.com returns the status of order #113 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform offering dozens of pay-per-call API endpoints 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/113/status` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maximum amount of 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which uses 6 decimals), equating to $0.02 per call. Payment is made via the x402 `exact` scheme, with a 300-second timeout. No API keys or rate limits are required; callers simply attach an X-PAYMENT header with a valid payment proof.
The platform's landing page lists additional endpoints for metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. Documentation pages beyond the landing page returned only a "Connect wallet" prompt with no further technical detail, so the actual response schema and behavior of this specific order-status endpoint remain undocumented.
Capabilities
Use cases
- —Checking the status of a specific order (#113) programmatically
- —Demonstrating x402 payment-gated API access on Base
- —Integrating low-cost per-call APIs without managing API keys
Fit
Best for
- —Agents or bots that need to query order status with instant crypto micropayments
- —Developers exploring x402 protocol integrations on Base
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 113)
- —Users who need detailed API documentation or response schemas before integrating
- —Non-crypto workflows that cannot produce x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/113/status \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/orders/113/status",
"method": "POST",
"headers": {
"X-PAYMENT": "<x402-payment-proof>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no response examples, no documentation beyond a landing page, and the endpoint appears to be hardcoded to a single order ID (113) with no explanation of what it actually returns. The docs, pricing, and README pages all returned only 'Connect wallet' with no content.
Warnings
- —No response schema or example response available — actual output format is unknown.
- —Endpoint is hardcoded to order ID 113; unclear if other order IDs are supported or how to discover them.
- —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no useful content.
- —The platform lists many endpoints on its landing page but none have documented schemas or examples.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base with a 300-second timeout.https://lowpaymentfee.com/api/v1/orders/113/status
- —The platform lists endpoints priced at $0.02 per request across data analytics, AI/ML, finance, and utility categories.https://lowpaymentfee.com
- —The platform advertises no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (Base mainnet USDC, 6 decimals).https://lowpaymentfee.com/api/v1/orders/113/status