x402basequality 0.35

Check order status via x402 micropayment on Base (USDC, $0.02/request).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

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

The specific resource `/api/v1/orders/73/status` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (contract 0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 "exact" scheme, with a 300-second timeout. No API keys or rate limits are required; callers simply attach a valid X-PAYMENT header.

The platform's landing page lists additional endpoints across four categories: Data & Analytics (metrics, reports, export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure (geocoding, validation, conversion, generation). All are uniformly priced at $0.02 per request. Documentation pages beyond the landing page were largely empty (showing only "Connect wallet"), so detailed request/response schemas for this or other endpoints are not available.

Capabilities

x402-paymentusdc-baseorder-statuspay-per-callno-api-keymicropayment

Use cases

  • Checking the status of a specific order via a single micropayment
  • Demonstrating x402 payment-gated API access patterns
  • Integrating pay-per-call order lookups into agent workflows

Fit

Best for

  • Developers experimenting with x402 payment protocols
  • Agents needing low-cost, keyless API access on Base
  • Prototyping micropayment-gated service architectures

Not for

  • Bulk order management or batch status queries
  • Users without USDC on the Base network
  • Production order tracking systems requiring documented schemas and SLAs

Quick start

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

Example

Request

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no response examples, no documentation beyond a landing page listing, and the specific endpoint path (/orders/73/status) appears to be a single hard-coded order ID with no explanation of its purpose or generalizability. Docs pages returned only 'Connect wallet' with no content.

Warnings

  • No OpenAPI or response schema available — request/response formats are unknown.
  • Documentation pages (/docs, /api, /pricing, /README) are effectively empty.
  • The endpoint path references a specific order ID (73); unclear if this generalizes to other order IDs.
  • The 'Premium API Access' label is generic and does not describe what data is returned.
  • Platform appears to be a demo or early-stage project with placeholder endpoints.

Citations

Provenance

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

Agent access