x402basequality 0.30

Check order status 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/109/status

What it does

This endpoint at lowpaymentfee.com returns the status of order #109 via a POST request, gated by an x402 payment challenge. It is part of a broader platform offering dozens 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/109/status` is listed under the title "Premium API Access." The x402 challenge confirms it is live, accepting exact-scheme payments of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to wallet `0x1A2B...85F3`. Payment is made via the `X-PAYMENT` header; no API keys or accounts are required. The response MIME type is `application/json`.

Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no usage examples. The endpoint path suggests it returns order status information, but the exact response shape is unknown. The broader platform advertises categories like sentiment analysis, text summarization, embeddings, geocoding, price feeds, and more, all at the same $0.02 price point.

Capabilities

x402-paymentusdc-baseorder-statuspay-per-requestno-api-keyjson-response

Use cases

  • —Checking the status of a specific order programmatically
  • —Demonstrating x402 payment-gated API access on Base
  • —Agent-driven order tracking with per-call USDC micropayments

Fit

Best for

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

Not for

  • —High-volume order management systems needing bulk queries
  • —Users who need detailed documentation or guaranteed SLAs
  • —Querying arbitrary order IDs (this endpoint is hardcoded to order 109)

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming pricing and network. However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty. The endpoint path is hardcoded to a single order ID (109), limiting general utility. Effectively a stub listing.

Warnings

  • —No OpenAPI spec or response schema available — response format is unknown
  • —Documentation pages (/docs, /pricing, /api, /README) all render only 'Connect wallet' with no content
  • —Endpoint is hardcoded to order ID 109; unclear if other order IDs are supported at different paths
  • —The broader platform lists many API categories but none have documented schemas

Citations

Provenance

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

Agent access

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