x402basequality 0.30

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 #149 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 across data analytics, AI/ML inference, finance/Web3, and infrastructure utility categories — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/149/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 X-PAYMENT header per the x402 protocol. There are no API keys, no rate limits, and no subscription commitments — callers pay per request.

Documentation on the site is extremely thin: the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the order status response contains. The endpoint path suggests it returns status information for a specific order (ID 149), but it is unclear whether the order ID is variable or hardcoded, and what fields the response includes. The platform appears to be a demonstration or early-stage x402 API marketplace.

Capabilities

x402-paymentusdc-basepay-per-requestorder-statusmicropayment

Use cases

  • Querying order status with a single micropayment, no subscription required
  • Demonstrating x402 protocol integration for agent-to-API payments
  • Testing pay-per-request patterns on the Base L2 network

Fit

Best for

  • Developers experimenting with x402 micropayment protocols
  • Agents needing stateless, keyless API access via crypto payments
  • Low-volume or sporadic order-status lookups without subscription overhead

Not for

  • High-volume order management systems needing bulk queries at lower per-call cost
  • Use cases requiring detailed API documentation or guaranteed SLAs
  • Applications that need to query arbitrary order IDs (unclear if endpoint supports variable IDs)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no OpenAPI schema, no request/response examples, and the docs pages are empty stubs. The endpoint path is hardcoded to a single order ID with no explanation of parameterization. Effectively a stub listing.

Warnings

  • Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no usable content
  • No OpenAPI or schema available — request body and response format are unknown
  • Endpoint path contains a hardcoded order ID (149); unclear if this is parameterizable
  • Platform appears to be early-stage or a demo; no SLA or support information available

Citations

Provenance

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

Agent access