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

What it does

This endpoint at lowpaymentfee.com returns the status of order #43 via an x402-gated POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI/ML inference, 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/43/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 a 300-second timeout. No API keys or rate limits are advertised; access is purely pay-per-request.

The platform's landing page lists 16 endpoints across four categories, all at the same $0.02 price point. Documentation pages (/docs, /pricing, /api, /README) returned only a "Connect wallet" prompt with no substantive content, so details about request/response schemas, error handling, or the actual data returned by this order-status endpoint are unknown. The endpoint is live (402 challenge captured successfully), but the lack of documentation makes it difficult to assess what the response payload contains or how to construct a meaningful request body.

Capabilities

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

Use cases

  • —Checking the status of a specific order programmatically
  • —Demonstrating x402 pay-per-request protocol integration
  • —Agent-driven order tracking with crypto micropayments

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing order status checks without API key management
  • —Crypto-native applications on Base network

Not for

  • —Production order management systems (single hardcoded order ID)
  • —Users needing detailed API documentation before integration
  • —Non-crypto payment workflows

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but the specific endpoint path (/orders/43/status) is hardcoded to a single order ID and is not listed among the platform's advertised APIs. Documentation pages are empty (just 'Connect wallet'). No request/response schema, no examples, and no explanation of what data is returned. The endpoint's purpose and utility are unclear.

Warnings

  • —This endpoint targets a single hardcoded order ID (43); unclear if it generalizes to other orders.
  • —No documentation available — /docs, /pricing, /api, and /README all return only 'Connect wallet'.
  • —No request or response schema provided; payload structure is unknown.
  • —This specific endpoint is not listed among the 16 APIs advertised on the landing page.

Citations

Provenance

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

Agent access

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