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

What it does

This endpoint at lowpaymentfee.com returns the status of order #164 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 infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

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

The broader platform advertises endpoints for sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. However, documentation beyond the landing page is extremely sparse: 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 actual data returned by this order-status endpoint is unknown beyond the MIME type (application/json).

Capabilities

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

Use cases

  • —Checking the status of a specific order (#164) programmatically
  • —Demonstrating x402 protocol micropayments on Base
  • —Agent-driven order status lookups without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-per-call API access
  • —Use cases requiring USDC micropayments on Base L2

Not for

  • —Production order management systems (endpoint is hardcoded to order 164)
  • —Users who need detailed API documentation or OpenAPI specs
  • —Bulk or high-volume order tracking across many order IDs

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, the endpoint is hardcoded to a single order ID, there is no OpenAPI spec, no request/response schema, and all documentation pages beyond the landing page are empty. The purpose and utility of this specific endpoint are unclear.

Warnings

  • —Endpoint is hardcoded to order ID 164 — unclear if other order IDs are supported or how to discover them
  • —No OpenAPI specification or request/response schema available
  • —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —The description 'Premium API Access' is generic and does not explain what data is returned
  • —No examples of successful responses are available anywhere in the crawled material

Citations

Provenance

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

Agent access

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