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 #117 via a POST request, gated by 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 settled in USDC on the Base network.
The specific resource `/api/v1/orders/117/status` accepts POST requests and requires an X-PAYMENT header carrying a valid x402 payment proof. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds. The response MIME type is application/json.
The platform advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /api, /README) all resolve but contain only a "Connect wallet" prompt with no substantive technical documentation. There is no OpenAPI spec, no request/response schema beyond the x402 challenge metadata, and no example payloads. The actual data returned by this order-status endpoint is unknown — it could be e-commerce order tracking or an internal demo resource. The endpoint is live and returning a well-formed x402 challenge.
Capabilities
Use cases
- —Querying order status with a single USDC micropayment on Base
- —Integrating pay-per-call order lookups into agent workflows
- —Demonstrating x402 protocol payment flows
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing keyless, pay-per-call API access on Base
- —Low-volume order status checks without subscription commitments
Not for
- —High-volume order management systems needing bulk queries
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/117/status
# Returns 402 with x402 challenge. Include X-PAYMENT header with valid payment proof to receive order status.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the purpose of this specific order-status resource is unclear. Effectively a stub listing.
Warnings
- —No OpenAPI or request/response schema available — actual payload structure is unknown
- —All documentation pages (/docs, /pricing, /api, /README) return only 'Connect wallet' with no technical content
- —The endpoint targets a hardcoded order ID (117); unclear whether this is a demo or production resource
- —No information on what data the order-status response actually contains
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base with asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/117/status
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform offers endpoints across Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com