x402basequality 0.35

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

What it does

This endpoint at lowpaymentfee.com returns the status of order #59 via a POST request, gated by an x402 payment challenge. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs — all priced at $0.02 per request, settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/59/status` accepts POST requests and requires an X-PAYMENT header containing a valid x402 payment proof. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the order status response actually contains. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what data is returned or what input parameters (if any) the POST body expects.

Capabilities

x402-paymentusdc-baseorder-statusmicropaymentpay-per-request

Use cases

  • —Checking the status of a specific order via programmatic API call
  • —Demonstrating x402 micropayment integration on Base network
  • —Agent-driven order tracking workflows that pay per request

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing pay-per-call order status lookups
  • —Projects wanting no-API-key, no-rate-limit access

Not for

  • —Production order management systems (endpoint is hardcoded to order #59)
  • —Users needing detailed API documentation or OpenAPI specs
  • —Bulk order status queries across many order IDs

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. No OpenAPI spec, no request/response schema, no examples. The endpoint is hardcoded to a single order ID (59), limiting general utility. Pricing is clear ($0.02/request in USDC on Base).

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all return only 'Connect wallet' with no content
  • —No OpenAPI or schema definition; request body and response format are unknown
  • —Endpoint is hardcoded to order ID 59; unclear if other order IDs are supported at different paths
  • —No examples of actual response data available

Citations

Provenance

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

Agent access

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