Discover / longwatch.dev

longwatch

■ Challenge detected

This-session snapshot only — no watch, no cursor. Use when you will not come back. Required by type: url/rss/x402 need url; price needs coin plus above, below, or move_pct_24h; edgar needs ticker or cik. 8-K items are decoded, Form 4 trades parsed, and x402 probes validate the unpaid 402 challenge without sending payment. If the job spans runs, create_watch instead and persist watch_id + key.

Listed price
$0.001
Challenge detected
1 of the last check
Median response
299 ms
Last checked
14 Oct, 18:06 UTC
In our index since
14 Oct 2026

Endpoint

curl -i https://longwatch.dev/check
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/longwatch.dev

Recent checks

14 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.14 Oct 2026
All 1 checks
When (UTC)ResultHTTPResponse
14 Oct, 18:06 UTCChallenge detected402299ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 14 Oct, 18:06 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What price is recorded for longwatch?

Its listed price is $0.001.

What payment terms does longwatch advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is longwatch listed?

In x402 Bazaar and x402-list.com. Superstables first indexed it on 14 Oct 2026.

Something wrong on this page? Tell us.