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 #191 via a pay-per-call x402 protocol. It is part of a broader platform offering various API categories including 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/191/status` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The cost per call is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. No API keys, rate limits, or subscriptions are required — each request is independently paid for on-chain.

The platform advertises a wide range of endpoints (sentiment analysis, text summarization, embeddings, price feeds, geocoding, etc.), all at the same $0.02 price point. However, documentation beyond the landing page is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no examples available. The actual data returned by this order-status endpoint is unknown beyond the fact that it serves application/json.

Capabilities

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

Use cases

  • Checking the status of a specific order (#191) via automated agent
  • Demonstrating x402 pay-per-call integration on Base network
  • Building payment-gated API workflows without API key management

Fit

Best for

  • Developers experimenting with x402 protocol payments
  • Agents that need to make one-off paid API calls without subscriptions
  • Use cases requiring no-signup, no-rate-limit API access

Not for

  • Production order management systems (endpoint is hardcoded to order 191)
  • Users needing detailed API documentation or OpenAPI specs
  • High-volume batch order status queries

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (returns a valid 402 x402 challenge), but documentation is nearly nonexistent — docs/pricing/API pages all show only 'Connect wallet'. The endpoint path is hardcoded to a single order ID (191), there is no OpenAPI spec, no request/response schema, and no examples. The purpose and utility of this specific endpoint are unclear beyond a generic 'Premium API Access' label.

Warnings

  • Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no technical content
  • Endpoint path is hardcoded to order 191 — unclear if this is a demo or a real resource
  • No OpenAPI spec or request/response schema available
  • No example responses documented; actual returned data is unknown
  • The broader platform lists many endpoints (AI, finance, utils) but none have documented schemas

Citations

Provenance

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

Agent access