x402basequality 0.35

x402-gated order status endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/orders/40/status

What it does

This endpoint at lowpaymentfee.com provides order status information via a pay-per-request x402 protocol. The specific resource `/api/v1/orders/40/status` returns order status data in JSON format when a valid x402 payment header is included. Payment is settled in USDC on the Base network.

The endpoint charges a maximum of 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The provider's site advertises a flat $0.02/request pricing model across all their APIs with no API keys, no rate limits, and instant access. The x402 challenge uses the "exact" payment scheme with a 300-second timeout.

The broader lowpaymentfee.com platform offers multiple API categories including Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure utilities (geocoding, validation, conversion, generation). All endpoints appear to follow the same $0.02/request pricing. However, this specific listing is for the order status endpoint only, and no detailed documentation about request/response schemas was found in the crawl.

Capabilities

x402-paymentusdc-settlementbase-networkorder-statuspay-per-requestjson-response

Use cases

  • —Checking the status of a specific order via a single paid API call
  • —Integrating order tracking into an agent workflow without API key management
  • —Demonstrating x402 protocol payment flows for commerce endpoints

Fit

Best for

  • —Agents needing on-demand order status without subscription overhead
  • —Developers experimenting with x402 pay-per-call protocols
  • —Low-volume order status lookups where per-request pricing is preferable

Not for

  • —High-volume order management systems needing bulk status checks
  • —Users who need detailed order modification or creation capabilities
  • —Applications requiring free or subscription-based access

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it works. However, there is no OpenAPI schema, no documentation about request body format or response structure, and the crawled docs/pricing/api pages all returned only 'Connect wallet' with no useful content. The endpoint path suggests a hardcoded order ID (40), which limits generality. Effectively a stub listing.

Warnings

  • —No request or response schema available — input/output formats are unknown
  • —The endpoint path includes a hardcoded order ID (/orders/40/status); unclear if this generalizes to other order IDs
  • —Documentation pages (/docs, /api, /pricing, /README) returned no meaningful content beyond 'Connect wallet'
  • —The nature of the 'order' being tracked is unspecified — could be a demo or placeholder

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/c9rVQn
x402-gated order status endpoint on Base, pay-per-call with USDC. — Clawmart · Clawmart