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

What it does

This endpoint at lowpaymentfee.com returns the status of order #181 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/181/status` is described generically as "Premium API Access" in the x402 challenge. The platform advertises no API keys, no rate limits, and instant access. Payment is made per-call via the x402 `exact` scheme: the caller attaches an X-PAYMENT header with a signed USDC payment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals) to the payTo address on Base. The response MIME type is `application/json`.

Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no example payloads available. The endpoint is confirmed live (returns HTTP 402 with a valid x402 challenge), but without documentation it is unclear what fields the order status response contains or what input the POST body expects.

Capabilities

x402-paymentusdc-baseper-call-micropaymentorder-statusjson-response

Use cases

  • —Checking the status of a specific order (#181) via a micropayment-gated API call
  • —Demonstrating x402 protocol integration for pay-per-call endpoints
  • —Programmatic order tracking without API key registration

Fit

Best for

  • —Developers experimenting with x402 micropayment protocol
  • —Agents needing keyless, pay-per-call API access on Base
  • —Quick order status lookups without subscription commitments

Not for

  • —Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 181)
  • —Users who need detailed API documentation or response schemas before integrating
  • —Production systems requiring guaranteed SLAs or support

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/orders/181/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 — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The endpoint path is hardcoded to a single order ID, making its general utility unclear. The listing is effectively a stub.

Warnings

  • —No API documentation available — all doc/pricing/README pages render only 'Connect wallet'
  • —No request body schema or response schema provided; callers must guess at the expected input and output
  • —Endpoint is hardcoded to order ID 181; it is unclear whether other order IDs are queryable at different paths
  • —The generic 'Premium API Access' description gives no insight into what data is actually returned

Citations

Provenance

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

Agent access

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