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 #51 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/51/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; authentication and billing are handled entirely through the x402 payment header. The platform advertises no rate limits, no minimums, and instant access.
Documentation is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no examples of what the order status response actually contains. The endpoint is live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know what payload to send or what response to expect.
Capabilities
Use cases
- —Checking the status of a specific order programmatically via a micropayment
- —Integrating pay-per-call order lookups into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on Base network
Fit
Best for
- —Agents or services that need on-demand order status without subscription commitments
- —Developers experimenting with x402 micropayment protocol integrations
- —Workflows requiring keyless, pay-as-you-go API access on Base
Not for
- —Bulk order tracking requiring thousands of lookups (no documented batch endpoint)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/51/status \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"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 path is hardcoded to a single order ID (51), making its general utility unclear. Pricing is clear ($0.02/request in USDC on Base).
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no usable content.
- —No OpenAPI or request/response schema available — callers cannot know what to send or what to expect back.
- —Endpoint path is hardcoded to order ID 51; it is unclear whether other order IDs are supported or how to discover them.
- —The 'Premium API Access' label is generic and does not describe the actual functionality.
Citations
- —The x402 challenge requires 20,000 base units of USDC on Base (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02 per request.https://lowpaymentfee.com/api/v1/orders/51/status
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, no minimums, and instant access on Base network.https://lowpaymentfee.com
- —Documentation, API, pricing, and README pages render only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs