x402basequality 0.35

Check order status via x402 micropayment on Base for $0.02 per request in USDC.

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

What it does

This endpoint at lowpaymentfee.com returns the status of a specific order (order ID 10 in the probed URL pattern) behind an x402 paywall. Payment is settled on the Base network using USDC (contract 0x8335…2913) with an exact-scheme challenge. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). The endpoint accepts POST requests and returns application/json.

The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto market data, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint being listed here is an order-status lookup, which does not clearly map to any of those advertised categories. Documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so the actual response schema and detailed behavior of this endpoint remain unknown.

Because there is no OpenAPI spec, no example responses, and no documentation beyond the landing page summary, the precise fields returned by this order-status endpoint cannot be confirmed. Agents should expect a JSON response but must handle unknown schema. The x402 challenge is live and well-formed.

Capabilities

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

Use cases

  • —Checking the status of an order programmatically via a single micropayment
  • —Integrating order-status lookups into an agent workflow without managing API keys
  • —Demonstrating x402 payment protocol usage on Base network

Fit

Best for

  • —Agents needing stateless, keyless order-status queries
  • —Developers experimenting with x402 micropayment protocols
  • —Low-volume, pay-as-you-go order tracking

Not for

  • —High-volume order management systems needing bulk queries at lower per-call cost
  • —Use cases requiring detailed API documentation or guaranteed SLAs
  • —Applications needing authentication, sessions, or persistent state

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payment. However, there is no OpenAPI spec, no response schema, no example responses, and all documentation pages are empty stubs ('Connect wallet'). The endpoint's actual functionality (order status for what system?) is unclear, and the URL appears to be a single hardcoded order ID rather than a parameterized resource.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all return only 'Connect wallet' with no content.
  • —Response schema is completely unknown; no examples or OpenAPI spec provided.
  • —The endpoint URL contains a hardcoded order ID (10); it is unclear whether this is parameterizable or a demo/test resource.
  • —The 'Premium API Access' title is generic and does not describe the endpoint's actual function.
  • —The broader platform advertises many API categories but none match 'order status', raising questions about what this endpoint actually returns.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/nQkuuk
Check order status via x402 micropayment on Base for $0.02 per request in USDC. — Clawmart · Clawmart