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

What it does

This endpoint at lowpaymentfee.com returns the status of order #160 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 utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/160/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 platform's landing page advertises additional endpoints across categories like sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, and more — all at the same $0.02 price point. However, documentation beyond the landing page is extremely sparse: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The actual data returned by this specific order-status endpoint is unknown beyond the MIME type (application/json).

Capabilities

x402-paymentusdc-baseorder-statuspay-per-callno-api-keymicropayment

Use cases

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

Fit

Best for

  • —Agents or services that need one-off order status checks without subscription overhead
  • —Developers experimenting with x402 protocol micropayments on Base
  • —Workflows requiring keyless, instant-access API calls

Not for

  • —Bulk or high-frequency order status polling (no documented batch endpoint)
  • —Users who need detailed API documentation or request/response schemas before integrating
  • —Non-crypto users who cannot settle payments in USDC on Base

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page, and the specific purpose of this order-status endpoint is opaque. The docs, pricing, and README pages are all empty stubs.

Warnings

  • —No OpenAPI or schema documentation available — request body and response format are entirely unknown.
  • —The /docs, /pricing, /api, and /README pages all render only 'Connect wallet' with no usable content.
  • —This endpoint is hardcoded to order ID 160; it is unclear whether other order IDs are supported or how to discover them.
  • —The platform lists many other endpoints on its landing page but none have documented schemas or examples.

Citations

Provenance

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

Agent access

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