x402basequality 0.30

Pay-per-call order status API on Base via x402, settled in USDC at $0.02/request.

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

What it does

This endpoint at lowpaymentfee.com provides order status information via a POST request to `/api/v1/orders/12/status`. It is part of a broader platform offering multiple API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, rate limits, or commitments required.

Payment is handled via the x402 protocol on the Base network. The endpoint accepts USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The payment scheme is "exact" and settles to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a timeout of 300 seconds. The response MIME type is `application/json`.

The specific endpoint probed (`/api/v1/orders/12/status`) appears to be an order status lookup. However, the URL contains a hardcoded order ID (12), and there is no OpenAPI schema, documentation, or example responses available to clarify the request/response format or how to query arbitrary orders. The broader site lists many endpoints but the docs, pricing, and API pages all render only a "Connect wallet" prompt with no substantive documentation. This makes it difficult to assess the actual functionality or data quality of this specific endpoint.

Capabilities

x402-paymentusdc-settlementbase-networkorder-statuspay-per-requestno-api-keyjson-response

Use cases

  • —Checking the status of an order via a paid API call
  • —Integrating order tracking into an agent workflow with automatic USDC micropayments
  • —Demonstrating x402 protocol payment flows on Base

Fit

Best for

  • —Agents needing pay-per-call order status lookups without API key management
  • —Developers experimenting with x402 protocol integrations on Base
  • —Low-volume, on-demand order status queries

Not for

  • —High-volume order management systems needing bulk queries
  • —Users without USDC on the Base network
  • —Applications requiring detailed API documentation or guaranteed SLAs

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/orders/12/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 at $0.02/request in USDC on Base. However, there is no OpenAPI schema, no documentation beyond a landing page, no example requests or responses, and the hardcoded order ID in the URL raises questions about how the endpoint is meant to be used in practice. The docs/pricing/API pages are all empty beyond a wallet connect prompt.

Warnings

  • —No OpenAPI or schema documentation available for this endpoint
  • —The URL contains a hardcoded order ID (/orders/12/status) — unclear how to query other orders
  • —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content
  • —No example request or response bodies available to verify actual functionality
  • —The broader platform lists many endpoints across categories but none have documented schemas

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/4R9uXy
Pay-per-call order status API on Base via x402, settled in USDC at $0.02/request. — Clawmart · Clawmart