x402basequality 0.30

x402-gated order status endpoint on Base, paying $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides order status information via an x402 payment-gated API. The specific resource `/api/v1/orders/91/status` returns order status data in JSON format when called with a valid x402 payment header. It is part of a broader platform that offers numerous pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request.

Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are advertised; access is granted purely through the x402 payment flow. The endpoint accepts POST requests and returns application/json responses.

Documentation on the site is extremely thin — the docs, pricing, API, 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 description of what fields the order status response contains. The endpoint path suggests it retrieves the status of a specific order (ID 91), but it is unclear whether this is a demo/sample resource or whether callers can substitute arbitrary order IDs. The platform appears to be a demonstration or early-stage deployment of x402-gated microservices.

Capabilities

x402-paymentusdc-baseorder-statuspay-per-requestno-api-key

Use cases

  • Checking the status of an order via a single paid API call
  • Demonstrating x402 payment-gated API access on Base
  • Integrating pay-per-request order lookups into agent workflows

Fit

Best for

  • Developers experimenting with x402 payment protocols
  • Agents needing stateless, keyless API access via crypto micropayments
  • Testing USDC-based pay-per-call patterns on Base

Not for

  • Production order management systems requiring documented schemas and SLAs
  • Users who need free or subscription-based API access
  • High-volume order tracking where $0.02 per call adds up

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/91/status \
  -H "X-PAYMENT: <x402-payment-header>" \
  -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, no documentation beyond a wallet-connect prompt, and the specific endpoint path (/orders/91/status) is opaque with no explanation of parameters or response shape. This is effectively a stub listing.

Warnings

  • No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
  • No OpenAPI or response schema provided; response format is unknown
  • Endpoint path references a hardcoded order ID (91); unclear if other IDs are supported
  • Platform appears to be early-stage or a demo; no SLA or support information available

Citations

Provenance

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

Agent access