x402-gated order status endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides order status lookups via the x402 payment protocol. The specific resource `/api/v1/orders/144/status` is a POST endpoint that returns order status information in JSON format, gated behind a per-request USDC micropayment on the Base network.
The endpoint is part of a broader platform (lowpaymentfee.com) that offers a variety of x402-gated APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments required.
The x402 challenge confirms the endpoint is live, accepting payments via the "exact" scheme on the Base network. Payment is made in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a maximum amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). The payment timeout is 300 seconds. Note that the specific endpoint path references a hardcoded order ID (144), so it is unclear whether this is a demo/example resource or whether callers are expected to substitute their own order IDs.
Capabilities
Use cases
- —Checking the status of an order via a pay-per-request model without needing API keys
- —Integrating order status lookups into agent workflows that support x402 payments
- —Demonstrating x402 micropayment protocol usage on the Base network
Fit
Best for
- —Agents or applications that support x402 payment protocol on Base
- —Developers exploring pay-per-call API patterns with USDC micropayments
- —Low-volume or sporadic order status queries where subscription pricing is wasteful
Not for
- —High-volume order management systems where per-request fees add up quickly
- —Users who need order status APIs without cryptocurrency payment capability
- —Production systems requiring documented request/response schemas and SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/144/status \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI schema, no documented request/response format, no examples, and the docs/pricing/API pages all returned only 'Connect wallet' with no useful content. The hardcoded order ID in the path raises questions about actual usage patterns.
Warnings
- —No request or response schema documented — input/output formats are unknown
- —Hardcoded order ID (144) in the endpoint path; unclear if this is a demo resource or parameterizable
- —Documentation pages (/docs, /api, /pricing, /README) returned no useful content beyond 'Connect wallet'
- —No OpenAPI spec or AI plugin manifest available
- —The broader platform lists many API categories but none have documented schemas or examples
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/orders/144/status
- —All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform offers APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/orders/144/status