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

What it does

This endpoint at lowpaymentfee.com returns the status of order #169 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/169/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 markets itself as requiring no API keys, no rate limits, and no commitments — just per-request micropayments. However, documentation is extremely thin: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no example request/response payloads, and no description of what the order status response actually contains. The endpoint path is hardcoded to order 169, so it is unclear whether this is a demo/sample endpoint or a production resource.

Capabilities

x402-paymentusdc-micropaymentbase-networkorder-statusper-request-billingno-api-key

Use cases

  • —Checking the status of a specific order via a single micropayment
  • —Demonstrating x402 payment-gated API access on Base
  • —Integrating pay-per-request order lookups into agent workflows

Fit

Best for

  • —Developers experimenting with x402 payment protocols
  • —Agents needing one-off order status checks without API key setup
  • —Prototyping micropayment-gated API patterns on Base

Not for

  • —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 169)
  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —Production order tracking systems requiring high reliability guarantees

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no example responses, and the endpoint path is hardcoded to a single order ID with no explanation of what data is returned or how to query other orders.

Warnings

  • —Documentation pages (/docs, /api, /pricing, /README) contain no substantive content — only 'Connect wallet' prompts.
  • —No OpenAPI or schema describing request body or response format.
  • —Endpoint is hardcoded to order ID 169; unclear if other order IDs are queryable or if this is a demo.
  • —No information about what the order status response payload contains.
  • —Platform lists many other API endpoints (AI, finance, utils) but this specific endpoint is an order status check — purpose and context are unclear.

Citations

Provenance

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

Agent access

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