x402basequality 0.30

Order status lookup via x402 micropayment on Base (USDC, $0.02/request).

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/orders/90/status

What it does

This endpoint at lowpaymentfee.com provides order status information for a specific order (order ID 90) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request, settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/90/status` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers attach an `X-PAYMENT` header containing a signed payment of up to 20,000 base units of USDC (i.e., $0.02, since USDC uses 6 decimals) to the payTo address on Base. No API keys, rate limits, or upfront commitments are required — each call is individually settled on-chain.

The platform advertises additional endpoints for metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. However, documentation beyond the landing page is extremely sparse (docs, API, pricing, and README pages all render only a "Connect wallet" prompt), so the actual response schema and behavior of this and other endpoints cannot be independently verified from the crawl material.

Capabilities

x402-paymentusdc-baseorder-statuspay-per-requestjson-responseno-api-key

Use cases

  • —Checking the status of a specific order programmatically
  • —Demonstrating x402 pay-per-request payment flows
  • —Integrating on-chain micropayment-gated API calls into agent workflows

Fit

Best for

  • —Developers experimenting with x402 protocol integration
  • —Agents that need to make small on-chain payments for API access
  • —Use cases requiring no-signup, no-API-key access to order data

Not for

  • —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 90)
  • —Users who need detailed API documentation or response schema guarantees
  • —Production systems requiring SLA-backed uptime and support

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/90/status \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <signed-x402-payment-header>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/orders/90/status
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (returns a valid 402 x402 challenge), but the specific resource is a single hardcoded order ID with no documented request/response schema. All documentation pages beyond the landing page are empty ('Connect wallet' only). No OpenAPI spec, no examples, and no way to verify what the endpoint actually returns upon successful payment.

Warnings

  • —Endpoint is scoped to a single hardcoded order ID (90); unclear if other order IDs are supported or how to discover them.
  • —All documentation pages (docs, API, pricing, README) return only 'Connect wallet' with no actual content.
  • —No OpenAPI spec or response schema available — response format is unknown.
  • —The broader platform advertises many endpoints (AI, finance, utils) but none can be verified from crawl data.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 06:21:18Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/VRh2FC
Order status lookup via x402 micropayment on Base (USDC, $0.02/request). — Clawmart · Clawmart