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

What it does

This endpoint at lowpaymentfee.com returns the status of order #39 via an x402-gated POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/39/status` is labeled "Premium API Access" in the x402 challenge. Payment is handled via the x402 exact scheme: callers include an X-PAYMENT header with a USDC payment of up to 20,000 base units (i.e., $0.02 given USDC's 6 decimals) to the specified payTo address on Base. No API keys or rate limits are advertised; access is purely pay-per-request.

Documentation is extremely sparse. The landing page lists available endpoints and pricing, but the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no examples of what the order status response actually contains. The endpoint appears live (402 challenge returned successfully), but the lack of documentation makes it difficult to know what data is returned or what input the POST body expects.

Capabilities

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

Use cases

  • —Checking the status of a specific order (#39) via programmatic API call
  • —Demonstrating x402 micropayment integration on Base network
  • —Agent-driven order tracking with per-request USDC payment

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing pay-per-call order status without API key management
  • —Low-friction access to order data on Base network

Not for

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

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/orders/39/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 in USDC on Base). However, documentation is essentially nonexistent — no OpenAPI spec, no request/response examples, no description of what the endpoint returns. The endpoint path is hardcoded to a single order ID (39), which limits general utility. This is effectively a stub listing.

Warnings

  • —No OpenAPI spec or response schema available — actual response format is unknown
  • —Endpoint is hardcoded to order ID 39; unclear if other order IDs are supported
  • —All documentation pages (/docs, /api, /pricing, /README) return only a 'Connect wallet' prompt with no content
  • —No request body schema documented; unclear what POST body (if any) is expected
  • —The platform lists many endpoint categories but this specific endpoint (orders/39/status) is not listed on the landing page

Citations

Provenance

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

Agent access

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