x402-gated order status endpoint on Base, pay-per-call with USDC.
What it does
This endpoint at lowpaymentfee.com provides order status lookups via the x402 payment protocol. The specific resource `/api/v1/orders/4/status` is accessed via POST and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 0.02 USDC per request (20,000 base units at 6 decimals).
The broader lowpaymentfee.com platform advertises a wide catalog of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, the specific endpoint being listed here is for order status retrieval, and no documentation beyond the landing page was available — the docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content.
Because there is no OpenAPI schema, no request/response examples, and no detailed documentation for this endpoint, the actual behavior and response format are unknown. The x402 challenge was successfully captured (HTTP 402), confirming the endpoint is live and accepting payment-gated requests.
Capabilities
Use cases
- —Checking the status of an order via a pay-per-call model without needing API keys
- —Integrating order tracking into agent workflows that can settle payments on Base with USDC
- —Demonstrating x402 protocol payment flows for commerce endpoints
Fit
Best for
- —Agents or services that need on-demand order status lookups with crypto micropayments
- —Developers exploring x402 protocol integrations on Base
- —Use cases where keyless, pay-per-request access is preferred over subscription billing
Not for
- —Users who need detailed API documentation or response schema guarantees before integrating
- —High-volume order tracking where $0.02 per request adds up significantly
- —Non-crypto workflows that cannot settle USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/4/status \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation, no request/response schema, and no examples. The docs pages are empty (just 'Connect wallet'). The endpoint path is hardcoded to a single order ID (/orders/4/status), which raises questions about general utility.
Warnings
- —No API documentation available — all doc pages return only 'Connect wallet' with no content
- —No OpenAPI schema or response examples; actual response format is unknown
- —Endpoint path is hardcoded to order ID 4 — unclear if this generalizes to other order IDs
- —The broader platform lists many endpoints but none have documented schemas or examples
Citations
- —The x402 challenge returns maxAmountRequired of 20000 in USDC (6 decimals) on Base, equaling $0.02 per requesthttps://lowpaymentfee.com/api/v1/orders/4/status
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/4/status