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

What it does

This endpoint at lowpaymentfee.com returns the status of order #141 via a POST request, gated by the x402 payment protocol. It accepts USDC payments on the Base network at $0.02 per call (20,000 base units of USDC with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof to access the resource.

The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request, settled in USDC on Base. However, the specific endpoint being listed here — `/api/v1/orders/141/status` — is an order-status lookup and does not appear in the site's public API catalog, so its exact response schema and purpose are unclear.

Documentation is extremely sparse: the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no example request/response payloads, and no detailed documentation for any endpoint. The x402 challenge is live and well-formed, confirming the endpoint is operational, 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-callno-api-keymicropayment

Use cases

  • —Checking the status of a specific order programmatically with per-call USDC payment
  • —Integrating x402-gated order lookups into agent workflows
  • —Demonstrating x402 payment protocol integration on Base

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-per-call API access on Base
  • —Micropayment-gated order status checks

Not for

  • —Production order management systems (endpoint is hardcoded to order 141)
  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —High-volume batch order lookups (no evidence of parameterized order IDs)

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint works. However, documentation is effectively nonexistent (all doc pages show only 'Connect wallet'), there is no OpenAPI spec, no example responses, and the endpoint path is hardcoded to a single order ID (141) with no indication of parameterization. The endpoint does not appear in the provider's own public API catalog.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all render only 'Connect wallet'
  • —No OpenAPI or schema describing request body or response format
  • —Endpoint is hardcoded to order ID 141; unclear if other order IDs are supported
  • —This specific endpoint (/api/v1/orders/141/status) is not listed in the provider's public API catalog
  • —No example request or response payloads available anywhere

Citations

Provenance

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

Agent access

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