x402basequality 0.25

Check order status via x402 micropayment on Base for $0.02 per request.

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

What it does

This endpoint at lowpaymentfee.com returns the status of order #31 via a POST request, gated by the x402 payment protocol. It is part of a broader platform that offers a variety of API categories — data & analytics, AI & machine learning, 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/31/status` accepts POST requests and requires an X-PAYMENT header containing a valid x402 payment proof. The maximum amount required is 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base), which equals $0.02 given USDC's 6 decimals. The payment timeout is 300 seconds. No API keys or rate limits are advertised; access is entirely pay-per-request.

Documentation on the site is extremely sparse — the docs, pricing, API, 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 description of what the order status response actually contains. The endpoint appears live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know what payload to send or what response to expect beyond the stated MIME type of application/json.

Capabilities

x402-paymentusdc-baseorder-statusmicropaymentpay-per-requestno-api-key

Use cases

  • —Checking the status of a specific order (#31) programmatically
  • —Demonstrating x402 micropayment integration on Base
  • —Agent-driven order tracking with per-request USDC payment

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need to check order status without API key management
  • —Low-volume, pay-as-you-go order status lookups

Not for

  • —High-volume order management systems (no bulk/batch support documented)
  • —Users who need detailed API documentation or response schema guarantees
  • —General-purpose order tracking across multiple order IDs (endpoint is hardcoded to order 31)

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but documentation is essentially nonexistent — no OpenAPI spec, no request/response examples, and all doc pages show only 'Connect wallet'. The endpoint path is hardcoded to a single order ID (31), making its general utility unclear. This is effectively a stub listing.

Warnings

  • —No API documentation available — docs, pricing, API, and README pages all render only 'Connect wallet'
  • —No OpenAPI or output schema provided beyond MIME type application/json
  • —Endpoint is hardcoded to order ID 31; unclear if other order IDs are supported at different paths
  • —No request body schema documented; unknown what POST payload is expected
  • —The broader platform advertises many API categories but none have documented schemas

Citations

Provenance

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

Agent access

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