x402basequality 0.25

Order status lookup via x402 micropayment on Base network, $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/orders/98/status

What it does

This endpoint at lowpaymentfee.com provides order status information behind an x402 paywall. The specific resource `/api/v1/orders/98/status` returns status data for order 98 when called via POST with a valid X-PAYMENT header. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) at a cost of $0.02 per request (20,000 base units with 6 decimals).

The provider lowpaymentfee.com hosts a broader suite of x402-gated APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are advertised at the same $0.02/request price point with no API keys, no rate limits, and instant access.

Documentation 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 schema, no request/response examples, and no explanation of what the order status response actually contains. The endpoint path suggests it is a demo or example resource (order ID 98 hardcoded in the URL). Without documentation it is unclear whether arbitrary order IDs can be queried or what fields the response includes.

Capabilities

x402-paymentusdc-base-networkorder-statusmicropaymentpay-per-requestno-api-key

Use cases

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

Fit

Best for

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

Not for

  • —High-volume order management systems needing bulk status checks
  • —Users who need detailed API documentation or guaranteed SLAs
  • —Production systems requiring well-documented request/response schemas

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live (returns 402 with 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 hardcoded order ID 98 in the path suggests a demo resource. The actual utility and response format are unknown.

Warnings

  • —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content.
  • —No OpenAPI or response schema available — response format is entirely unknown.
  • —The endpoint path contains a hardcoded order ID (98); it is unclear if this is a demo or if arbitrary IDs are supported.
  • —No request body schema documented; unclear what (if any) POST body is expected.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/JGdexT
Order status lookup via x402 micropayment on Base network, $0.02 per request in USDC. — Clawmart · Clawmart