x402basequality 0.30

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

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

What it does

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

The specific endpoint `/api/v1/orders/199/status` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds.

The platform advertises no API keys, no rate limits, and instant access. However, documentation beyond the landing page is essentially empty (all doc/pricing/API pages just show a "Connect wallet" prompt), so the actual response schema and behavior of this endpoint are not documented. It is unclear whether this is a demo/placeholder endpoint or a production service. The order ID (199) is hardcoded in the URL, suggesting this may be a specific resource lookup rather than a general-purpose API.

Capabilities

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

Use cases

  • —Checking the status of a specific order via a single micropayment
  • —Demonstrating x402 protocol payment flows on Base
  • —Agent-driven order tracking with per-call USDC settlement

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need to query order status without API key registration
  • —Low-volume, pay-as-you-go order lookups

Not for

  • —High-volume order management systems needing bulk queries
  • —Users who need detailed API documentation or response schema guarantees
  • —General-purpose order tracking across multiple order IDs (endpoint is hardcoded to order 199)

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is effectively nonexistent — all pages beyond the landing page show only 'Connect wallet'. No response schema, no request body schema, and no example responses are available. The hardcoded order ID (199) raises questions about general utility.

Warnings

  • —Documentation pages (/docs, /api, /pricing, /README) are all empty beyond a 'Connect wallet' prompt
  • —No response schema or example responses available
  • —Endpoint URL contains a hardcoded order ID (199); unclear if other order IDs are supported
  • —Platform appears to be a demo or early-stage project with minimal documentation

Citations

Provenance

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

Agent access

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