x402basequality 0.25

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

What it does

This endpoint at lowpaymentfee.com returns the status of order #14 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/14/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. No API keys or rate limits are advertised; access is granted per-call by attaching an X-PAYMENT header with a valid x402 payment proof. The timeout for payment settlement is 300 seconds.

Documentation on the site is extremely thin — 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, and no example payloads available. The endpoint is live (returns 402 as expected), but without documentation it is unclear what fields the order status response contains or what input body (if any) the POST expects. The platform appears to be a demonstration or early-stage x402 marketplace rather than a mature production API.

Capabilities

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

Use cases

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

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing stateless, keyless API access via crypto micropayments
  • —Prototyping pay-per-call commerce APIs on Base

Not for

  • —Production order management systems requiring documented schemas and SLAs
  • —Bulk order status queries where per-call pricing is inefficient
  • —Users without a Base-network USDC wallet

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page listing, and the endpoint path is hardcoded to a single order ID. This is effectively a stub listing.

Warnings

  • —No OpenAPI spec or request/response schema available
  • —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —Endpoint path is hardcoded to order ID 14 — unclear if other order IDs are supported
  • —Platform appears to be a demo or very early-stage project
  • —No examples of actual response payloads exist in crawled material

Citations

Provenance

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

Agent access

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