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 #156 via an x402-gated POST request. It is part of a broader platform that offers a variety of API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/156/status` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: the endpoint returns a 402 challenge with payment details, and the caller includes an `X-PAYMENT` header to authorize a USDC micropayment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals). Payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, with a timeout of 300 seconds. No API keys or rate limits are advertised; access is instant upon payment.

The platform's landing page lists many other endpoints across analytics, AI (sentiment analysis, summarization, classification, embeddings), finance (price feeds, exchange rates, token quotes, gas estimates), and infrastructure (geocoding, validation, conversion, generation), all at the same $0.02 price point. However, the crawled documentation pages (`/docs`, `/api`, `/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 not documented.

Capabilities

x402-paymentusdc-micropaymentbase-networkorder-statusjson-responseno-api-keypay-per-request

Use cases

  • Checking the status of a specific order (#156) via a single micropayment
  • Demonstrating x402 payment-gated API access on Base
  • Integrating pay-per-call order tracking into an agent workflow

Fit

Best for

  • Developers experimenting with x402 micropayment protocols
  • Agents that need to pay per API call without API key management
  • Low-volume, on-demand order status lookups

Not for

  • High-volume order management systems needing bulk status checks
  • Users who need detailed order history or modification capabilities
  • Anyone without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/156/status
# Returns 402 with x402 challenge. Include X-PAYMENT header with signed USDC payment to complete the request.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but the specific order-status endpoint is narrow (hardcoded order #156), documentation pages are empty (only 'Connect wallet'), and there is no response schema, example payloads, or explanation of what the order status response contains. Effectively a stub listing.

Warnings

  • Documentation pages (/docs, /api, /pricing, /README) all returned only 'Connect wallet' with no usable content.
  • The endpoint path is hardcoded to order #156 — unclear if other order IDs are supported or if this is a demo.
  • No response schema or example response is available; actual output format is unknown.
  • No OpenAPI spec or AI plugin manifest found.

Citations

Provenance

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

Agent access