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
Endpoint
https://lowpaymentfee.com/api/v1/orders/119/status

What it does

This endpoint at lowpaymentfee.com returns the status of order #119 via a POST request, gated behind an x402 payment challenge. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/119/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 (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base), which equals $0.02 given USDC's 6 decimals. No API keys are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof. The platform advertises no rate limits, no minimums, and instant access.

Documentation is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the order status response contains. The endpoint is confirmed live (returns HTTP 402 with a well-formed x402 challenge), but the actual functionality behind the paywall is opaque from available materials.

Capabilities

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

Use cases

  • —Checking the status of a specific order (#119) programmatically
  • —Demonstrating x402 micropayment integration on Base
  • —Agent-driven order tracking without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-call order status lookups
  • —Projects already using USDC on Base network

Not for

  • —Production order management systems (endpoint is hardcoded to order 119)
  • —Users who need detailed API documentation or response schemas
  • —Anyone without USDC on Base network

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/orders/119/status
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent (all doc pages show only 'Connect wallet'). There is no OpenAPI schema, no request/response examples, and the endpoint is hardcoded to a single order ID (119), making its general utility unclear. The broader platform lists many endpoints but provides no substantive documentation for any of them.

Warnings

  • —Documentation pages (/docs, /api, /pricing, /README) contain no useful content — only a 'Connect wallet' prompt.
  • —No OpenAPI or schema available; request and response formats are unknown.
  • —Endpoint is hardcoded to order ID 119 — unclear if this is a demo or a real resource.
  • —No information about what data the order status response actually contains.
  • —The broader platform advertises many API categories (AI, finance, analytics, etc.) but none have documented schemas or examples.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/kkhfb4
Check order status via x402 micropayment on Base network for $0.02 per request. — Clawmart · Clawmart