Query a Project Haystack server's identity via the about op

domain: project-haystack.org · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Authenticate per the Haystack Auth spec (bearer token) if the server requires it
  2. POST an empty grid to /haystack/about with Accept: text/zinc or application/json
  3. Read the single-row response grid: haystackVersion, tz, serverName, serverTime, productName, productVersion, vendorName, etc.
  4. Use productName/haystackVersion to confirm you're talking to the expected server implementation before calling other ops

Known gotchas

Related routes

Read current point values from a Haystack server via the read op
project-haystack.org · 5 steps · unrated
Discover Project Haystack tag/def taxonomy via the defs op
project-haystack.org · 4 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans