x402basequality 0.30

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

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

What it does

This endpoint at lowpaymentfee.com returns the status of order #71 via an x402-gated POST request. It is part of a broader platform that offers a variety of pay-per-call APIs spanning 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/71/status` is labeled "Premium API Access" in the x402 challenge. The payment scheme is "exact" with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 protocol's X-PAYMENT header, with no API keys or rate limits required. The endpoint accepts POST requests and returns application/json.

The broader platform advertises endpoints for sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, validation, conversion, and more — all at the same $0.02 price point. However, documentation beyond the landing page is extremely sparse: the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the order status response actually contains. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what data is returned or what input the POST body expects.

Capabilities

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

Use cases

  • —Checking the status of a specific order via a single micropayment
  • —Integrating order status lookups into an agent workflow without API key management
  • —Demonstrating x402 protocol payment flows on Base network

Fit

Best for

  • —Agents needing keyless, pay-per-call order status checks
  • —Developers experimenting with x402 micropayment protocol
  • —Workflows requiring no subscription or rate-limit constraints

Not for

  • —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 71)
  • —Use cases requiring detailed API documentation or guaranteed SLAs
  • —Production systems needing well-documented request/response schemas

Quick start

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

Endpoint

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

Quality

0.30/ 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 spec, no request/response schema, no documentation beyond a landing page, and the endpoint path is hardcoded to a single order ID (71), making its general utility unclear. The docs, pricing, and README pages are all empty stubs.

Warnings

  • —No OpenAPI or schema documentation available — request body and response format are unknown
  • —Endpoint path is hardcoded to order 71; unclear if other order IDs are supported or how to discover them
  • —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
  • —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:20:20Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

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