x402basequality 0.35

Check order status via x402 micropayment on Base network for $0.02 per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

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

The specific endpoint `/api/v1/orders/70/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 x402 protocol's X-PAYMENT header, with no API keys or rate limits required. The endpoint accepts POST requests and returns application/json.

The platform's landing page advertises a wide catalog of endpoints (metrics, reports, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, validation, etc.), all at the same $0.02 price point. However, documentation pages beyond the landing page returned only a "Connect wallet" prompt with no substantive content, so detailed request/response schemas for this or any other endpoint are unavailable.

Capabilities

x402-paymentorder-statususdc-basepay-per-callno-api-keyjson-response

Use cases

  • Checking the status of a specific order programmatically with per-call payment
  • Integrating order status lookups into agent workflows without managing API keys
  • Demonstrating x402 payment protocol integration on Base network

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing keyless, pay-per-call order status checks
  • Low-volume order status queries without subscription commitments

Not for

  • High-volume order management systems needing bulk status queries
  • Users who need detailed API documentation and response schemas before integrating
  • Querying orders other than order #70 (endpoint is hardcoded to a single order ID)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, the endpoint path is hardcoded to a single order ID, documentation pages are empty (only 'Connect wallet'), and no request/response schemas or examples are available. The purpose and utility of this specific endpoint are unclear.

Warnings

  • Endpoint is hardcoded to order #70 — unclear if other order IDs are supported or how to discover them.
  • All documentation, pricing, and README pages returned only 'Connect wallet' with no substantive content.
  • No OpenAPI spec, request schema, or response schema is available — request/response format is unknown.
  • 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:30:35Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access