x402basequality 0.25

Check order status via x402 micropayment on Base (USDC, $0.02/request).

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

What it does

This endpoint at lowpaymentfee.com returns the status of order #175 via a POST request, gated by an x402 payment challenge. It is part of a broader platform offering dozens 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/175/status` appears to be an order-status lookup. The x402 challenge confirms it is live, accepting USDC (contract 0x8335…2913) on Base with a max amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). Payment is made via the `exact` scheme with a 300-second timeout. No API keys or rate limits are advertised; access is granted per-request upon payment.

Documentation on the site 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 spec, no request/response schema beyond the x402 challenge's `outputSchema` stub, and no examples of what the order-status response actually contains. The platform lists many other endpoints (sentiment analysis, summarization, embeddings, price feeds, geocoding, etc.) at the same $0.02 price point, but none have documented schemas either. Treat this listing as a stub until richer documentation is published.

Capabilities

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

Use cases

  • —Checking the fulfillment or processing status of a specific order
  • —Demonstrating x402 payment-gated API access on Base
  • —Integrating pay-per-call order lookups into agent workflows

Fit

Best for

  • —Developers experimenting with x402 payment protocols
  • —Agents that need on-demand order status without API key management
  • —Low-volume, pay-as-you-go order tracking

Not for

  • —High-volume order management systems needing bulk queries
  • —Users who need detailed order-status response schemas before integrating
  • —Anyone without a Base-network USDC wallet

Quick start

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

Example

Request

{
  "url": "https://lowpaymentfee.com/api/v1/orders/175/status",
  "method": "POST",
  "headers": {
    "X-PAYMENT": "<x402_payment_token>",
    "Content-Type": "application/json"
  }
}

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no response schema, no examples, and the docs pages are empty. The specific endpoint path (/orders/175/status) is hard-coded to a single order ID, which limits general usefulness. Effectively a stub.

Warnings

  • —No OpenAPI spec or response schema available — response format is unknown
  • —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
  • —The endpoint path is hard-coded to order ID 175; unclear if other order IDs are supported or how to discover them
  • —Platform lists many endpoints but none have documented request/response contracts

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/hzqAmd
Check order status via x402 micropayment on Base (USDC, $0.02/request). — Clawmart · Clawmart