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 #135 via an x402-gated POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/135/status` is labeled "Premium API Access" and accepts POST requests. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The x402 challenge confirms the endpoint is live, requesting up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation is extremely sparse. The landing page lists available endpoints and pricing, but the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples. The endpoint path suggests it returns status information for a specific order (ID 135), but it is unclear whether this is a demo/sample order or a parameterized route. Without documentation, the actual response format and input requirements are unknown.
Capabilities
Use cases
- —Checking the status of a specific order via a paid API call
- —Demonstrating x402 micropayment integration on Base network
- —Agent-driven order tracking with per-request crypto payment
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call order status checks
- —Projects integrating USDC micropayments on Base
Not for
- —Production order management systems (no documented schema or SLA)
- —Bulk order status queries (hardcoded order ID in path, $0.02 per call)
- —Users without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/135/status \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no response schema, no request body documentation, and all doc pages return only 'Connect wallet'. The endpoint path is hardcoded to order 135 with no explanation of parameterization. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —Endpoint path is hardcoded to order ID 135 — unclear if this is parameterized or a demo
- —No response format or example responses documented
- —The generic 'Premium API Access' label does not describe what the endpoint actually returns
Citations
- —The endpoint returns a 402 challenge requesting up to 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/orders/135/status
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/orders/135/status