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 #161 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint `/api/v1/orders/161/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 (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base), which equals $0.02 given USDC's 6 decimals. No API keys are required; access is granted per-call by including the X-PAYMENT header with a valid x402 payment proof. The platform advertises no rate limits and instant access.
Documentation is extremely sparse — 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 examples beyond the landing page's list of available endpoints. The endpoint is live (returns a proper 402 challenge), but the actual response payload for a paid request is unknown. The order-status endpoint appears to be a specific resource (order 161) rather than a general-purpose API, which limits its utility unless the caller knows the context of that order.
Capabilities
Use cases
- —Checking the status of a specific order (#161) on the lowpaymentfee platform
- —Demonstrating x402 payment-gated API access on Base network
- —Integrating pay-per-call order lookups into agent workflows
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need to make one-off paid API calls without API key management
- —Low-volume, on-demand order status checks
Not for
- —General-purpose order management (this is a single fixed order resource)
- —Users who need detailed API documentation or response schemas before integrating
- —High-volume order tracking requiring bulk or subscription-based access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/161/status \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The endpoint targets a single hardcoded order resource (order 161), making its general utility unclear.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all render only 'Connect wallet'
- —No OpenAPI or response schema provided; actual response format is unknown
- —Endpoint targets a specific order (#161) rather than a parameterized resource — unclear general utility
- —The platform lists many API categories on its landing page but none have documented schemas
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/orders/161/status
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/161/status
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) show only 'Connect wallet'https://lowpaymentfee.com/docs