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

What it does

This endpoint at lowpaymentfee.com returns the status of order #158 via a POST request, gated by the x402 payment protocol. It is one of many endpoints offered by the lowpaymentfee.com platform, which provides a broad catalog 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/158/status` is described as "Premium API Access" in the x402 challenge. The challenge confirms the endpoint is live, accepting POST requests, and requires an exact-scheme x402 payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to the address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The payment timeout is 300 seconds.

Documentation on the site is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The platform advertises no API keys, no rate limits, and instant access, but the actual response format and fields for this order-status endpoint are unknown.

Capabilities

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

Use cases

  • —Checking the status of a specific order (#158) via automated agent
  • —Demonstrating x402 payment-gated API access on Base
  • —Integrating pay-per-call order tracking into a workflow

Fit

Best for

  • —Agents needing x402-compatible order status checks
  • —Developers experimenting with x402 micropayment protocol on Base
  • —Use cases requiring no-signup, pay-per-call API access

Not for

  • —Querying arbitrary order IDs (this endpoint is hardcoded to order 158)
  • —Users who need detailed API documentation or response schemas before integrating
  • —High-volume order tracking where per-request fees add up

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The endpoint path is hardcoded to a single order ID (158), limiting general utility. Docs pages are empty beyond a wallet-connect prompt.

Warnings

  • —No OpenAPI spec or response schema available — actual response format is unknown.
  • —Endpoint is hardcoded to order ID 158; unclear if other order IDs are supported at different paths.
  • —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content.
  • —The platform lists many other endpoints but none have documented schemas either.

Citations

Provenance

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

Agent access

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