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 #36 via an x402-gated POST request. It is part of a broader platform that exposes dozens of API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.
The specific resource `/api/v1/orders/36/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 per the x402 protocol (version 1), with a 300-second timeout. No API keys or rate limits are advertised; access is purely pay-per-call.
Documentation is extremely sparse — 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 beyond the x402 challenge's outputSchema stub, and no explanation of what the order status response actually contains. The platform lists many other endpoints on its landing page but provides no detailed documentation for any of them.
Capabilities
Use cases
- —Querying order status behind a micropayment wall
- —Demonstrating x402 protocol integration for pay-per-request APIs
- —Agent-driven order tracking with crypto-settled access
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need to pay per API call without API keys
- —Low-cost order status lookups settled on Base
Not for
- —Production order management systems (no documented response schema)
- —Users who need detailed API documentation or SDKs
- —High-volume batch queries where per-request payment overhead is impractical
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/36/status
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment to access.Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge), but there is no OpenAPI spec, no response schema, no documentation beyond a wallet-connect prompt, and the endpoint path is hardcoded to a single order ID. Effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet'
- —No OpenAPI or response schema provided; response format is unknown
- —Endpoint path is hardcoded to order 36 — unclear if this generalizes to other order IDs
- —The platform lists many endpoints on its landing page but none have documented request/response contracts
Citations
- —maxAmountRequired is 20000 base units of USDC on Base, equaling $0.02 per requesthttps://lowpaymentfee.com/api/v1/orders/36/status
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/36/status