x402basequality 0.35

Check order status 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/186/status

What it does

This endpoint at lowpaymentfee.com returns the status of order #186 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/186/status` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, 6 decimals), which equals $0.02. Payment is made via the x402 exact scheme with no API keys, no rate limits, and no upfront commitments required. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, and the timeout window is 300 seconds.

The platform's landing page lists 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, no OpenAPI schema, detailed documentation, or example responses were found in the crawl; the docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. The actual data returned by this order-status endpoint is unknown beyond the stated mimeType of application/json.

Capabilities

x402-paymentusdc-baseorder-statuspay-per-requestno-api-keymicropayment

Use cases

  • —Checking the status of a specific order (#186) programmatically
  • —Demonstrating x402 pay-per-request payment flows on Base
  • —Integrating low-cost API calls settled in USDC without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing simple pay-per-call access without subscriptions
  • —Web3-native applications that can settle in USDC on Base

Not for

  • —Users needing bulk or high-throughput order management (single hardcoded order ID)
  • —Anyone without a Base-compatible USDC wallet
  • —Production order-tracking systems requiring documented response schemas

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/186/status \
  -H "X-PAYMENT: <x402_payment_token>" \
  -H "Content-Type: application/json"

Endpoint

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

Quality

0.35/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no documented request/response format, no example payloads, and the docs pages are empty. The endpoint path is hardcoded to a single order ID (186), making its general utility unclear.

Warnings

  • —No OpenAPI or response schema available — actual response format is unknown
  • —Documentation pages (/docs, /api, /pricing, /README) all return only 'Connect wallet' with no content
  • —Endpoint path is hardcoded to order ID 186; unclear if other order IDs are supported or if this is a demo
  • —The 'Premium API Access' label is generic and does not describe what data is actually returned

Citations

Provenance

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

Agent access

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