x402basequality 0.35

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

What it does

This endpoint at lowpaymentfee.com returns the status of order #95 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/95/status` is labeled "Premium API Access" and requires a one-time x402 payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, using the USDC contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. The x402 challenge uses the "exact" scheme with a 300-second timeout. No API keys or rate limits are advertised; access is instant upon payment.

The platform's landing page lists additional endpoints for metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. However, documentation pages (docs, pricing, README) returned only a "Connect wallet" prompt with no further technical detail, so the actual response schema and behavior of this specific order-status endpoint are unknown.

Capabilities

x402-paymentusdc-baseorder-statuspay-per-callmicropayment

Use cases

  • —Checking the status of a specific order (#95) programmatically
  • —Demonstrating x402 payment-gated API access on Base
  • —Agent-driven order tracking with per-call USDC micropayments

Fit

Best for

  • —Developers experimenting with x402 payment protocols
  • —Agents needing pay-per-call order status lookups
  • —Projects wanting no-API-key, no-rate-limit access patterns

Not for

  • —Bulk order management across many order IDs (endpoint is hardcoded to order 95)
  • —Users who need detailed API documentation or response schemas before integrating
  • —Non-crypto users who cannot settle payments in USDC on Base

Quick start

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

Example

Request

{
  "url": "https://lowpaymentfee.com/api/v1/orders/95/status",
  "method": "POST",
  "headers": {
    "X-PAYMENT": "<x402-payment-token>",
    "Content-Type": "application/json"
  }
}

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but the endpoint is hardcoded to a single order ID, no response schema or documentation is available, and all doc/pricing/README pages returned only 'Connect wallet' with no content. The actual utility and response format are unknown.

Warnings

  • —Endpoint is hardcoded to order ID 95 — unclear if other order IDs are supported or how to parameterize.
  • —No documentation available: /docs, /pricing, and /README pages all return only 'Connect wallet'.
  • —Response schema is completely unknown — no outputSchema fields beyond the input method.
  • —The 'Premium API Access' label is generic and does not describe what data is actually returned.

Citations

Provenance

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

Agent access

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