x402basequality 0.30

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

What it does

This endpoint at lowpaymentfee.com returns the status of order #166 via an x402-gated POST request. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/166/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. Payment is made via the x402 protocol's X-PAYMENT header, with no API keys or rate limits required. The endpoint accepts POST requests and returns application/json.

Note that while the platform advertises many endpoint categories (analytics, AI, finance, infrastructure), the specific endpoint being listed here is an order-status lookup. Documentation beyond the landing page 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 documentation, and no example payloads available. The endpoint is confirmed live (402 challenge captured successfully).

Capabilities

x402-paymentusdc-baseorder-statuspay-per-requestno-api-keyjson-response

Use cases

  • —Checking the status of a specific order (#166) programmatically
  • —Demonstrating x402 micropayment integration on Base
  • —Agent-driven order tracking with per-call USDC payment

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need to check order status without API key management
  • —Low-friction pay-per-use API access on Base

Not for

  • —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 166)
  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —Non-crypto users who cannot pay in USDC on Base

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — no request/response schemas, no OpenAPI spec, and all doc pages render only 'Connect wallet'. The endpoint path is hardcoded to a single order ID (166), making its general utility unclear. Pricing is clear ($0.02/request in USDC on Base).

Warnings

  • —No API documentation available; /docs, /pricing, /api, and /README pages all show only 'Connect wallet'
  • —Endpoint is hardcoded to order ID 166 — unclear if other order IDs are supported or how to discover them
  • —No request body schema or response schema documented anywhere
  • —The 'Premium API Access' label is generic and does not describe what the endpoint actually returns
  • —Platform advertises many API categories but no evidence any of them have real backing services

Citations

Provenance

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

Agent access

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