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 #137 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 infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/137/status` appears to be an order-status lookup. The x402 challenge confirms it is live, accepting payment of up to 20,000 base units of USDC (0.02 USD) on Base to address 0x1A2B…85F3. No API keys or rate limits are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof. The response MIME type is application/json.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no usage examples. The endpoint path suggests it returns order status information, but the exact fields and semantics are unknown. The platform advertises many other endpoints (sentiment analysis, summarization, geocoding, etc.) at the same $0.02 price point, but none have documented schemas either.
Capabilities
Use cases
- —Checking the status of a specific order (#137) programmatically
- —Demonstrating x402 micropayment integration on Base
- —Agent-driven order tracking with per-call USDC payment
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need to query order status without API keys
- —Low-friction pay-per-use API access on Base
Not for
- —Production order management systems (endpoint is hardcoded to order 137)
- —Users who need documented request/response schemas before integrating
- —High-volume batch order lookups (no bulk endpoint available)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/137/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), but there is no OpenAPI spec, no documented request/response schema, no examples, and the endpoint is hardcoded to a single order ID. Documentation pages are effectively empty. This is a stub-level listing.
Warnings
- —No OpenAPI spec or response schema available — response format is unknown
- —Endpoint is hardcoded to order 137; unclear if other order IDs are supported via different paths
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content
- —The broader platform advertises many endpoints but none have documented schemas
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/orders/137/status
- —All endpoints on the platform are priced at $0.02 per request with no API keys or rate limitshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/137/status
- —Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/orders/137/status