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 #180 via a POST request, gated by 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/180/status` accepts POST requests and requires an X-PAYMENT header containing 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 300-second timeout.
The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (docs, pricing, README) all resolve to a minimal "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is live (returns 402 as expected), but the actual response format after successful payment is unknown.
Capabilities
Use cases
- —Checking the status of a specific order (#180) programmatically
- —Demonstrating x402 micropayment integration on Base
- —Agent-driven order status polling with per-request USDC payment
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to query order status and can pay per call in USDC
- —Low-friction API access without API key management
Not for
- —Bulk order status queries across many order IDs (endpoint is hardcoded to order 180)
- —Users who need detailed API documentation or response schemas before integrating
- —Non-crypto payment workflows
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/180/status \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially absent — all doc/pricing/README pages show only 'Connect wallet'. No OpenAPI spec, no request/response schemas, and the endpoint path is hardcoded to a single order ID (180), making its general utility unclear. Pricing is clear ($0.02) but everything else must be inferred.
Warnings
- —Documentation pages (/docs, /pricing, /README) contain no usable content — only a 'Connect wallet' prompt.
- —No OpenAPI or schema documentation is available; response format after payment is unknown.
- —The endpoint path is hardcoded to order ID 180 — it is unclear whether other order IDs are supported or how to discover them.
- —The platform lists many other API categories (AI, finance, analytics) but this specific endpoint is an order status check with no clear relationship to those categories.
Citations
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The x402 challenge specifies maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network with a 300-second timeout.https://lowpaymentfee.com/api/v1/orders/180/status
- —The platform offers endpoints across data & analytics, AI & ML, finance & Web3, and infrastructure categories.https://lowpaymentfee.com