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 #92 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs — all priced at $0.02 per request, payable in USDC on the Base network with no API keys, rate limits, or commitments required.

The specific endpoint `/api/v1/orders/92/status` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (asset 0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. The response MIME type is application/json.

Note that this endpoint is scoped to a single order ID (92). The broader platform lists many other endpoints across categories like sentiment analysis, text summarization, embeddings, price feeds, gas estimates, geocoding, and more — all at the same $0.02 price point. Documentation pages beyond the landing page returned only a "Connect wallet" prompt with no further technical detail, so the actual response schema and request body format for this endpoint remain undocumented.

Capabilities

x402-paymentusdc-baseorder-statusmicropaymentno-api-keypay-per-request

Use cases

  • Checking the status of a specific order programmatically with per-request USDC payment
  • Demonstrating x402 protocol micropayment flows on Base
  • Integrating pay-per-use order tracking into agent workflows

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing on-demand order status without API key management
  • Low-volume, pay-as-you-go API consumption on Base

Not for

  • High-volume order management systems needing bulk queries
  • Users who need detailed API documentation or response schemas before integrating
  • Querying arbitrary order IDs (this endpoint is hardcoded to order 92)

Quick start

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

Endpoint

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). However, there is no documentation on request body format, response schema, or what data is actually returned. The endpoint is scoped to a single hardcoded order ID with no explanation. Docs pages returned only 'Connect wallet' with no content.

Warnings

  • Endpoint is hardcoded to order ID 92 — unclear if other order IDs are available or how to discover them.
  • No request body schema or response schema documented anywhere.
  • All documentation pages beyond the landing page returned only 'Connect wallet' with no usable content.
  • The 'Premium API Access' label is generic and does not describe the actual functionality.

Citations

Provenance

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

Agent access