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/97/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 suite of x402-gated APIs spanning data analytics (metrics, reports, data export, insights), AI/ML (sentiment analysis, text summarization, classification, embeddings), finance/Web3 (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.
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 usage examples available. The endpoint is confirmed live (returns a valid x402 402 challenge), but the actual data returned upon successful payment is unknown. The order ID "97" in the URL path suggests this may be a specific resource lookup rather than a general-purpose API.
Capabilities
Use cases
- —Checking the status of a specific order via programmatic pay-per-call access
- —Integrating order tracking into an agent workflow that can settle USDC on Base
- —Demonstrating x402 protocol payment flows for commerce endpoints
Fit
Best for
- —Agents or services that need on-demand order status without API key management
- —Developers experimenting with x402 payment protocol integrations
- —Workflows requiring low-cost per-call access to order data
Not for
- —Users needing comprehensive order management (create, update, cancel)
- —Anyone requiring detailed API documentation or response schema guarantees before integrating
- —High-volume batch order lookups where per-call pricing may add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/97/status \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI spec, no documented request/response schema, no usage examples, and the docs pages are empty. The specific endpoint path (/orders/97/status) appears to be a single hardcoded resource rather than a parameterized API. Pricing is clear but everything else must be inferred.
Warnings
- —No OpenAPI spec or schema documentation available
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The endpoint path contains a hardcoded order ID (97), unclear if this is parameterizable
- —No response schema or example responses are documented anywhere
- —The actual data returned upon successful payment is completely unknown
Citations
- —Endpoint returns a valid x402 402 challenge with USDC on Base network, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/orders/97/status
- —All endpoints listed at $0.02 per request with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Platform advertises 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/97/status