x402-gated order status endpoint on Base, pay-per-call with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to order status information via the x402 payment protocol. The specific resource `/api/v1/orders/68/status` is a POST endpoint that returns order status data in JSON format, gated behind a per-request USDC micropayment on the Base network.
The endpoint charges a maximum of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). Payment is handled 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 advertised; access is purely payment-gated.
The broader lowpaymentfee.com platform advertises a suite of x402-gated APIs spanning data/analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all at the same $0.02/request price point. However, this specific listing covers only the `/api/v1/orders/68/status` endpoint. Documentation beyond the landing page is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content.
Capabilities
Use cases
- —Checking the status of a specific order via a single paid API call
- —Integrating pay-per-request order lookups into agent workflows
- —Demonstrating x402 payment protocol integration on Base
Fit
Best for
- —Agents or services that need on-demand order status without subscription commitments
- —Developers experimenting with x402 micropayment-gated APIs
- —Low-volume, pay-as-you-go order tracking
Not for
- —High-volume order management systems needing bulk or subscription pricing
- —Users who need detailed API documentation or OpenAPI schemas before integrating
- —Querying arbitrary order IDs (this endpoint is hardcoded to order 68)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/orders/68/status \
-H "X-PAYMENT: <x402-signed-payment>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge), and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documentation of request/response formats, no example payloads, and the endpoint path is hardcoded to a single order ID (68), making its general utility unclear. Docs pages are empty beyond a wallet-connect prompt.
Warnings
- —Endpoint path is hardcoded to order ID 68 — unclear if other order IDs are supported or how to discover them.
- —No OpenAPI spec, no request/response schema, and no example payloads are available.
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no substantive content.
- —The broader platform advertises many API categories (AI, finance, infrastructure) but none have documented schemas or verifiable functionality.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/orders/68/status
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/orders/68/status
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages show only 'Connect wallet'https://lowpaymentfee.com/docs