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

What it does

This endpoint at lowpaymentfee.com returns the status of order #122 via an x402-gated POST request. It is part of a broader platform that offers a variety of API endpoints across data & analytics, AI & machine learning, finance & Web3, and infrastructure categories — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/122/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 (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), which equals $0.02 given USDC's 6 decimals. The payment timeout is 300 seconds.

The platform advertises no API keys, no rate limits, and instant access. However, documentation is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no explanation of what data the order status endpoint actually returns or what input it expects beyond a POST body. The endpoint path is hardcoded to order 122, which raises questions about whether this is a demo/example or a genuinely useful production endpoint.

Capabilities

x402-paymentusdc-baseorder-statusmicropaymentjson-responsepost-method

Use cases

  • —Checking the status of a specific order via a paid API call
  • —Demonstrating x402 micropayment integration on Base
  • —Agent-driven order tracking with per-request USDC payment

Fit

Best for

  • —Developers experimenting with x402 protocol payments
  • —Agents that need to pay per API call without API keys
  • —Testing micropayment flows on Base network

Not for

  • —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 122)
  • —Users who need comprehensive API documentation or OpenAPI specs
  • —Production order tracking systems requiring reliability guarantees

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (returns a valid 402 x402 challenge) and pricing is clear ($0.02 USDC on Base). However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the endpoint is hardcoded to a single order ID (122), making its practical utility unclear. This is effectively a stub listing.

Warnings

  • —Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no actual content
  • —No OpenAPI or schema documentation available
  • —Endpoint is hardcoded to order ID 122 — unclear if other order IDs are supported or how to discover them
  • —No request body schema or response examples available
  • —Platform appears to be a demo or early-stage project

Citations

Provenance

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

Agent access

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