Subscribe to live point updates via Haystack watchSub and watchPoll
domain: project-haystack.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to /haystack/watchSub with a watchDis display string and rows of id Refs to open a new watch, optionally requesting a lease duration
Capture the watchId and server-assigned lease from the response grid meta — servers may ignore a requested lease
If subscribed entities proxy an external source (e.g. a Haystack-to-BACnet gateway), watchSub should trigger a downstream refresh (poll or COV) on that source
Poll with watchPoll using the watchId meta tag; add a refresh meta tag to force a full re-read instead of changes-only
Add more entities to the same watch by resending watchSub with the existing watchId; close it with watchUnsub and the close meta tag
Known gotchas
An error-grid response from watchSub/watchPoll means the watch is no longer valid — open a new watch rather than retrying the same watchId
The id used in the watchSub request may not equal the canonical id returned in the response/poll rows — map by row order, not by echoed id
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?