x402basequality 0.35

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/129/status

What it does

This endpoint at lowpaymentfee.com returns the status of order #129 via an x402-gated POST request. It is part of a broader platform that offers a variety of API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/129/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. No API keys or rate limits are advertised; access is granted per-request via the x402 payment protocol with a 300-second timeout.

The platform's landing page lists 16 endpoints spanning metrics, reports, data export, insights, sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, token quotes, gas estimates, geocoding, validation, conversion, and generation — all at the same $0.02 price point. Documentation pages beyond the landing page returned only a "Connect wallet" prompt with no further technical detail, so the actual request/response schemas for this and other endpoints remain undocumented.

Capabilities

x402-paymentorder-statususdc-basemicropaymentper-request-billingno-api-key

Use cases

  • —Checking the status of a specific order via a single paid API call
  • —Demonstrating x402 micropayment integration on the Base network
  • —Agent-driven order tracking workflows that pay per request

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing pay-per-call order status checks without API keys
  • —Low-volume, on-demand order status queries

Not for

  • —High-volume order management systems needing bulk status checks
  • —Users who need detailed API documentation and response schemas before integrating
  • —Querying arbitrary order IDs (this endpoint is hardcoded to order 129)

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, there is no OpenAPI schema, no documented request/response format, and the docs pages are empty stubs. The endpoint is also hardcoded to a single order ID (129), making its general utility unclear.

Warnings

  • —Documentation pages (/docs, /api, /pricing, /README) all return only 'Connect wallet' with no technical content.
  • —No request or response schema is documented — input/output formats are unknown.
  • —The endpoint path is hardcoded to order ID 129; it is unclear whether other order IDs are supported or how to discover them.
  • —The platform lists many endpoints on its landing page but none have published documentation beyond a title and price.

Citations

Provenance

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

Agent access

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