x402basequality 0.35

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/86/status

What it does

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

The specific endpoint `/api/v1/orders/86/status` is described as "Premium API Access" and accepts POST requests. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The challenge specifies an exact-scheme payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is directed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (docs, pricing, API reference) all resolve to minimal "Connect wallet" stubs with no substantive content. There is no OpenAPI schema, no example request/response payloads, and no detailed documentation for what the order status response actually contains. The endpoint appears live (402 challenge returned successfully), but the lack of documentation makes it difficult to assess the actual utility or data format returned.

Capabilities

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

Use cases

  • —Checking the status of a specific order via a single micropayment
  • —Integrating pay-per-call order lookups into agent workflows
  • —Demonstrating x402 protocol payment flows on Base

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing one-off order status checks without API key management
  • —Low-volume, pay-as-you-go API consumption

Not for

  • —High-volume order management systems needing bulk queries
  • —Users who need detailed API documentation before integrating
  • —Production systems requiring SLA guarantees or support

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no example request/response, and all documentation pages are empty stubs ('Connect wallet'). The specific endpoint path (/orders/86/status) is hardcoded to a single order ID, which limits general utility. Effectively a stub listing.

Warnings

  • —Documentation pages (/docs, /pricing, /api, /README) all return empty 'Connect wallet' stubs with no actual content
  • —No OpenAPI or schema describing request parameters or response format
  • —Endpoint is hardcoded to order ID 86 — unclear if this is a demo or a real resource
  • —No information on what data the order status response actually contains
  • —Platform lists many other endpoints on its homepage but none have documented schemas

Citations

Provenance

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

Agent access

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