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

What it does

This endpoint at lowpaymentfee.com returns the status of order #106 via a POST request, gated by 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/106/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 or rate limits are advertised; access is granted per-call via the x402 payment header. The challenge specifies a maximum timeout of 300 seconds.

Documentation on the site is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available from the crawl. The endpoint is live (returns a proper 402 challenge), but the actual response payload structure for a successful paid call is unknown.

Capabilities

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

Use cases

  • —Checking the status of a specific order (#106) programmatically
  • —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 can settle USDC micropayments on Base
  • —Use cases requiring keyless, per-call API access

Not for

  • —Bulk order status queries across many order IDs (only order 106 is exposed at this URL)
  • —Users who need detailed API documentation or response schemas before integrating
  • —Non-crypto payment workflows

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no examples. The endpoint path is hardcoded to a single order ID (106), and the broader platform pages render only wallet-connect prompts. This is effectively a stub listing.

Warnings

  • —No API documentation available; /docs, /api, /pricing, and /README pages all show only 'Connect wallet'
  • —No OpenAPI or output schema provided — response format for a successful paid call is unknown
  • —Endpoint path is hardcoded to order 106; unclear if other order IDs are accessible or if this is a demo
  • —The platform lists many other endpoints (AI, finance, analytics) but this listing covers only /api/v1/orders/106/status

Citations

Provenance

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

Agent access

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