x402basequality 0.30

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

What it does

This endpoint at lowpaymentfee.com returns the status of order #46 via a POST request, gated behind 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/46/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-request upon payment. The x402 challenge was confirmed live, returning a proper 402 with version 1 challenge metadata.

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 examples beyond the landing page's list of endpoints. The endpoint path suggests it retrieves the status of a specific order (order ID 46), but without documentation it is unclear what the response payload looks like or whether the order ID is parameterized.

Capabilities

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

Use cases

  • —Checking the status of a specific order via a single micropayment
  • —Integrating pay-per-call order tracking into an agent workflow
  • —Demonstrating x402 protocol payment flows on Base

Fit

Best for

  • —Agents needing one-off order status lookups without subscription overhead
  • —Developers experimenting with x402 payment-gated APIs
  • —Use cases where no API key management is desired

Not for

  • —Bulk order management or batch status queries (no documented batch support)
  • —Users who need detailed API documentation or response schemas before integrating
  • —Production systems requiring SLA guarantees (no docs on uptime or support)

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — docs/pricing/API pages all show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The endpoint path is hardcoded to order 46, making its general utility unclear.

Warnings

  • —No API documentation available — docs, pricing, and README pages render only 'Connect wallet'
  • —No OpenAPI or output schema provided beyond the x402 challenge metadata
  • —Endpoint path is hardcoded to order ID 46; unclear if this is parameterizable
  • —Response format and fields are completely undocumented

Citations

Provenance

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

Agent access

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