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 #136 via a POST request, gated by an x402 payment challenge. It is part of a broader platform offering dozens of pay-per-call 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 endpoint `/api/v1/orders/136/status` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (token contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 exact scheme — callers attach an X-PAYMENT header with a signed payment to the specified payTo address. No API keys or rate limits are required; access is instant once payment is included.
Documentation is extremely sparse. The landing page lists available endpoints and pricing, but 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 documentation, and no usage examples. The endpoint is confirmed live (returns HTTP 402 with a valid x402 challenge), but the actual response payload for a successful paid request is unknown.
Capabilities
Use cases
- —Checking the status of a specific order (#136) via programmatic API call
- —Demonstrating x402 payment-gated API access on Base
- —Integrating micropayment-based API calls into agent workflows
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call API access without API keys
- —Low-cost micropayment API consumption on Base L2
Not for
- —Production order management systems (endpoint is hardcoded to order 136)
- —Users needing detailed API documentation or OpenAPI specs
- —Bulk or high-throughput order status queries
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/136/status \
-H "X-PAYMENT: <x402-signed-payment>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. The endpoint path is hardcoded to a single order ID (136), there is no OpenAPI spec, no request/response schema, and no examples. The purpose and utility of this specific endpoint are unclear beyond a demo.
Warnings
- —No documentation available — /docs, /pricing, /api, /README all render only 'Connect wallet'
- —Endpoint path is hardcoded to order #136; unclear if other order IDs are supported or how to discover them
- —No OpenAPI spec or response schema provided
- —No request body schema documented; unknown what (if any) POST body is expected
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/orders/136/status
- —All endpoints on the platform are priced at $0.02 per requesthttps://lowpaymentfee.com
- —No API keys, no rate limits, instant access advertisedhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/orders/136/status
- —Documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet'https://lowpaymentfee.com/docs