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 #67 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 across data analytics, AI/ML inference, finance/Web3, and infrastructure utility categories — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/67/status` is labeled "Premium API Access" in the x402 challenge. The payment scheme is "exact" with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the X-PAYMENT header to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout.
The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (/docs, /pricing, /api, /README) all resolve to a minimal "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation describing what fields the order status response contains or what input parameters are expected. The endpoint path is hardcoded to order 67, so it is unclear whether this is a demo/sample endpoint or whether other order IDs are queryable at similar paths.
Capabilities
Use cases
- —Checking the status of a specific order via a single paid API call
- —Demonstrating x402 payment protocol integration for agent-to-agent commerce
- —Programmatic order tracking without API key registration
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents needing stateless, keyless API access to order data
- —Quick integration where no signup or subscription is desired
Not for
- —Production order management systems requiring bulk or batch status queries
- —Users who need detailed API documentation and response schemas before integrating
- —Anyone needing to query arbitrary order IDs (endpoint is hardcoded to order 67)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/67/status \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on request parameters, response schema, or what 'order 67 status' actually returns. All doc pages are empty stubs. The hardcoded order ID raises questions about general usability.
Warnings
- —All documentation pages (/docs, /pricing, /api, /README) return only 'Connect wallet' with no actual content
- —No OpenAPI schema or response examples available
- —Endpoint path is hardcoded to order ID 67 — unclear if other order IDs are supported
- —No request body schema documented; input parameters unknown
- —The 'Premium API Access' label is generic and does not describe the actual functionality
Citations
- —The x402 challenge requires 20,000 base units of USDC on Base, equaling $0.02 per requesthttps://lowpaymentfee.com/api/v1/orders/67/status
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/67/status
- —Payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/orders/67/status
- —Documentation pages resolve to minimal 'Connect wallet' prompt with no substantive contenthttps://lowpaymentfee.com/docs