Slack vs Zulip

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Slack
   Slack✓fullprobed8/10

   Slack has a confirmed llms.txt at docs.slack.dev/llms.txt (HTTP 200) plus llms-full-deno.txt variants, and its developer docs are explicitly agent-oriented (MCP server, AI build guides, quickstart) suitable for pointing an agent at. missing for 10: no independent/community confirmation of an agent successfully consuming llms.txt in practice, and OpenAPI-style machine spec endpoints under docs.slack.dev returned 404.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.slack.dev/llms.txt # Slack Developer Docs > The official documentation for building on the Slack p…”
   • [claimed-docs] “Once connected, your AI assistant can search channels, read messages, and use real conversation context to help you build.”
   • [claimed-docs] “You can create Slack-hosted workflows written in TypeScript using the Deno Slack SDK.”
   • [probe] “official MCP server documented at https://docs.slack.dev/ai/slack-mcp-server/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Zulip~partialprobed3/10

   No llms.txt exists (confirmed 404) and other agent-friendly doc endpoints (openapi.json, docs.md) also 404 on the primary domain, but Zulip does publish a full machine-readable OpenAPI spec in its GitHub repo that an agent could be pointed at to understand the API surface. This is a weak substitute for a true llms.txt/agent-docs entry point. Missing for 10: an actual llms.txt file, any officially surfaced agent-oriented documentation page, and discoverability of the OpenAPI spec from the main docs site rather than only via GitHub raw.

   • [probe] “PROBE llms.txt: HTTP 404 at https://zulip.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://zulip.com/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://zulip.com/openapi.json, https://zulip.com/swagger.json, https://zulip.com/api/openapi.json, …”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack's Web API (chat.postMessage etc.) is a pure HTTP interface callable without any UI, the Events API supports webhook/Socket Mode server-side listening, Workflow Builder supports webhook triggers to kick off automations from outside Slack, and the Slack CLI/Bolt SDKs let apps be built, deployed, and run non-interactively — all enabling headless automation suitable for CI-like use. Missing for 10: explicit CI/CD pipeline examples (e.g. GitHub Actions integration), and no documentation of running the CLI/SDKs specifically inside a CI runner or headless test harness.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Zulip~partialprobed6/10

   Zulip ships a documented REST API (OpenAPI spec verified live), a keyless-working API endpoint, and an official Python CLI (zulip-send) that installs via pip and runs headlessly from scripts, supporting basic CI automation like sending messages. However, there's no evidence of first-class CI/CD integration patterns, GitHub Actions examples, containerized headless server mode, or broader automation tooling beyond bots/webhooks. missing for 10: CI-specific documentation or examples, containerized/headless deployment guidance for automation pipelines, evidence of use in real CI workflows.

   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”
   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Slack
   Slack✓fullprobed8/10

   Slack publishes an official MCP server (docs.slack.dev/ai/slack-mcp-server/) that lets MCP clients/agents search channels, send/draft messages, manage canvases, lists, files, and users, with admin approval controls for governance; this is corroborated by a direct probe confirming the docs page exists. Missing for 10: independent hands-on third-party verification of the MCP server's real-world reliability/performance beyond first-party docs.

   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Send messages — send messages to any type of conversation in Slack.”
   • [claimed-docs] “Create and read lists — create lists with custom schemas and read their contents.”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “Draft messages — draft, format, and preview messages directly within AI clients.”
   • [probe] “official MCP server documented at https://docs.slack.dev/ai/slack-mcp-server/”

   proof ↗⚑ flag

   Zulip—none0/10

   Zulip is a chat platform, so publishing an official MCP server to let AI agents connect is a plausible axis, but no evidence pack item mentions MCP at all — only bots, webhooks, REST API, and OpenAPI spec are documented. missing for 10: any mention of an MCP server (official or community), MCP protocol support, or agent-connection tooling beyond generic bots/API.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Slack
   Slack✓fullprobed8/10

   Slack ships an official CLI for building/managing Slack apps (slack-docs-9, slack-docs-1, slack-docs-26/40/60, slack-probe-4), with quickstart guides supporting Bolt frameworks in multiple languages, tied into an AI-native workflow (docs mention creating agents via 'slack create' and building AI-integrated apps). Missing for 10: independent/hands-on community corroboration of the CLI itself (community evidence in the pack is unrelated to CLI usage) and more detail on AI-native-specific CLI commands beyond scaffolding.

   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “Download the command-line tool for developing Slack apps.”
   • [claimed-docs] “Set up a new Bolt project from a starter template. `slack create`”
   • [claimed-docs] “slack create”
   • [claimed-docs] “Set up a new Bolt project from a starter template.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [probe] “official CLI documented at https://docs.slack.dev/tools/slack-cli/”

   proof ↗⚑ flag

   Zulip~partialprobed6/10

   Hands-on evidence confirms an official 'zulip-send' CLI installs via PyPI and runs headlessly for scripting message sends, which supports agentic/automation use cases. However, the evidence pack shows no broader CLI feature set (e.g., reading messages, managing channels, bots) beyond sending, and no first-party docs elaborating CLI capabilities beyond the probe. Missing for 10: documented full CLI command reference, evidence of read/administrative CLI operations, and independent community corroboration of CLI use in agentic workflows.

   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Slack✓fullprobed9/10

   Slack ships extensive documented public APIs (Web API with 200+ methods, Events API, Bolt/CLI SDKs, official OpenAPI/AsyncAPI specs in slackapi/slack-api-specs) plus an official MCP server enabling AI-native agents to search, message, upload files, manage lists/canvases — all first-party documented and independently verifiable via the public GitHub spec repo. missing for 10: no independent hands-on report specifically confirming the raw REST/Web API (vs MCP) working end-to-end from a third-party AI integrator, and the docs.slack.dev/openapi.json probe returned 404 suggesting the interactive spec isn't hosted at the expected discovery path.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “official MCP server documented at https://docs.slack.dev/ai/slack-mcp-server/”
   • [probe] “official CLI documented at https://docs.slack.dev/tools/slack-cli/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Zulip✓fullprobed9/10

   Zulip publishes a documented REST API (zulip.com/api) backed by a full OpenAPI 3.0 spec in its repo, verified live against a public server responding to documented endpoints, plus an official Python CLI (zulip-send) installable via pip for scripting/automation. This directly supports an AI-native user driving the product programmatically. Missing for 10: no discoverable llms.txt or machine-readable docs endpoint for LLM consumption, and no independent third-party corroboration beyond hands-on probes.

   • [claimed-docs] “Send a message”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Slack
   Slack~partialclaimed4/10

   Slack's API model implies scoped bot/user tokens (the OpenAPI spec notes 'user and bot user token usage of public Web API methods') and admin approval of MCP client integrations is described as keeping data safe, suggesting some governance over agent access, but there is no explicit documentation of an OAuth-scopes system or a user-facing flow to mint least-privilege credentials specifically for an agent. Missing for 10: explicit OAuth scope list/granularity docs, a documented workflow for a user to generate a scoped token for an agent, and any admin/user UI for restricting agent permissions beyond MCP client approval.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”

   proof ↗⚑ flag

   Zulip—none0/10

   Zulip documents bot accounts and API keys for automation, but no evidence shows a mechanism for issuing scoped or least-privilege credentials (e.g., restricted permission bots, granular API scopes) specifically for AI agents — bots appear to get a single API key without documented fine-grained access controls.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Slack
   Slack✓fullclaimed9/10

   Slack ships multiple official SDKs (Bolt for Java, node-slack-sdk, Deno Slack SDK), an official CLI, Web API with published OpenAPI spec, Events API, and Block Kit docs, all clearly documented as first-party developer tooling for building AI-native/agentic integrations, plus a developer sandbox for safe testing. Missing for 10: independent/hands-on developer corroboration beyond official docs and a fully discoverable OpenAPI endpoint (probe found candidate paths 404 despite spec repo existing).

   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “You can create Slack-hosted workflows written in TypeScript using the Deno Slack SDK.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “Whether you're composing layouts for modals, messages, or tabs, the Block Kit building experience is the same — your app will be sculpting s…”

   proof ↗⚑ flag

   Zulip✓fullprobed8/10

   Zulip ships an official Python SDK/CLI installable via PyPI (pip install zulip) with hands-on verified functionality (zulip-send), a full machine-readable OpenAPI 3.0.1 spec covering the REST API, and a live documented REST API confirmed working on a public server. This directly satisfies building against official SDKs for an AI-native/agentic workflow. Missing for 10: no evidence of SDKs in other languages (JS/Node, Go, etc.), no llms.txt or dedicated agent-facing docs, and no independent third-party corroboration of SDK quality beyond the hands-on probe.

   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”
   • [claimed-docs] “Send a message”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Events API lets developers subscribe to specific event types via webhook (public HTTP endpoint) or Socket Mode, with Slack calling the subscriber's endpoint on events — a core webhook-subscription mechanism well documented for building AI/agentic integrations. Workflow Builder also supports webhook triggers for starting workflows externally, reinforcing webhook-based event subscription. missing for 10: independent/hands-on corroboration of webhook reliability at scale, and more explicit framing of Events API webhooks specifically for AI-native/agent consumption (most AI-agent docs emphasize MCP/Web API rather than raw event webhooks).

   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Webhook triggers for workflows”

   proof ↗⚑ flag

   Zulip—none0/10

   Evidence only shows Zulip supports *incoming* webhooks for pushing external events into Zulip (zulip-docs-19) and a bot framework for reacting to messages (zulip-docs-4/12/24), but nothing documents an outgoing webhook mechanism for an AI-native user to subscribe to Zulip's own events. missing for 10: documentation of outgoing/subscription webhooks, event-type configuration, or webhook payload schema for external consumers.

   • [claimed-docs] “Incoming webhooks”
   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack ships built-in AI features (intelligent daily briefing, Slackbot summaries/recaps, channel/thread summarization, workspace-wide semantic search across integrated data, meeting notes from huddles) that surface AI-generated insights directly inside the product, per slack-docs-13/14/15/16/19/34/52. missing for 10: independent/hands-on verification of insight quality and accuracy, and detail on how suggestions are surfaced/actioned beyond marketing copy.

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Conversations with coworkers, PDFs, images for your social campaign, decks buried in Google Drive, support tickets, customer records from Sa…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “if it's shared in or integrated into Slack, it's searchable.”

   proof ↗⚑ flag

   Zulip—none0/10

   No evidence of any AI-generated insights, summarization, or suggestion features surfaced within Zulip itself; evidence covers topics, channels, search, bots (rule-based), integrations, and hosting/export, none of which involve AI analysis of data. Missing for 10: any AI summarization/insight feature, AI-generated suggestions, or documented AI assistant surfaced in the product UI.

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack's Workflow Builder lets users build no-code automations with triggers (including webhook triggers from outside Slack) and conditional branching that run autonomously in the background once configured, and the Events API/CLI/Bolt frameworks let developers build bots/apps that respond to activity without manual intervention. This directly satisfies the 'autonomous background automation' story for AI-native and non-technical users alike. missing for 10: independent/hands-on verification that these automations run reliably unattended over time, and explicit AI-agent-triggered automation examples beyond marketing copy

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”
   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”

   proof ↗⚑ flag

   Zulip~partialprobed5/10

   Zulip supports bots that run autonomously in the background via its bot API framework and Botserver for production deployment, plus a full REST/OpenAPI API and CLI tools for scripting automations. However, this is a general chatbot/integration framework rather than an AI-native agentic automation platform with built-in scheduling, triggers, or autonomous task orchestration. Missing for 10: evidence of AI-specific agent orchestration, native scheduling/triggering beyond message-reactive bots, and independent hands-on validation that bots run reliably unattended in production.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Slack
   Slack✓fullclaimed7/10

   Slack ships Slackbot as a built-in AI agent that can summarize channels, prepare meeting briefs, analyze reports, answer open-ended questions, and act on tasks like updating deals or routing work to other agents (slack-docs-13,14,15,38,55,57,69). This is a native, in-product delegation capability, not just a third-party integration. Missing for 10: independent/hands-on user reports confirming Slackbot's agentic task delegation works as advertised, and more detail on the scope of actions it can autonomously perform beyond summarization/Q&A.

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Update deals just by asking Slackbot”
   • [claimed-docs] “Slackbot can now dig deep on open-ended questions, not just quick ones.”
   • [claimed-docs] “Slackbot just got a full-screen workspace built for deeper work.”
   • [claimed-docs] “Route work through Slackbot. Coordinate work by routing requests to agents and get results delivered right back into your workflow.”

   proof ↗⚑ flag

   Zulip—none0/10

   Zulip's evidence covers bots/integrations built by users via its API, but there is no mention of a built-in AI assistant that users can delegate tasks to directly within the product.

   ⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack ships Slackbot as an in-product AI agent that responds to natural-language requests (e.g., 'Update deals just by asking Slackbot', daily briefings, summarization, open-ended Q&A) and exposes an official MCP server so AI assistants can search, message, and manage Slack objects via natural language. This directly supports NL-command operation for AI-native users. missing for 10: independent/hands-on validation of Slackbot NL command accuracy and reliability, and clearer documentation of the scope/limits of what natural-language commands can trigger (vs. workflow builder's no-code but still menu-driven automations).

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Update deals just by asking Slackbot”
   • [claimed-docs] “Slackbot can now dig deep on open-ended questions, not just quick ones.”
   • [claimed-docs] “Slackbot just got a full-screen workspace built for deeper work.”
   • [claimed-docs] “AI agents can now read, write, and manage your Slack Lists directly.”
   • [claimed-docs] “Once connected, your AI assistant can search channels, read messages, and use real conversation context to help you build.”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”

   proof ↗⚑ flag

   Zulip—none0/10

   Zulip's docs describe channels, topics, search filters, and a bot API for building reactive bots, but none of this constitutes an AI-native natural-language command interface for operating the product itself — no evidence of NLU-driven commands, AI assistant, or agentic control layer. missing for 10: any natural-language command parsing/interface, AI assistant for operating Zulip, evidence of NL-driven actions beyond keyword search filters.

   • [claimed-docs] “channel:design has:image new logo: Search for messages in #design that include an image and contain the keywords new and logo.”
   • [claimed-docs] “Zulip also offers a wide array of search filters, which can be used on their own, or in combination with keywords.”
   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Zulip
   Slack—none0/10

   Slack has API method reference docs (e.g. chat.postMessage) and an OpenAPI/AsyncAPI spec repo, but there is no evidence of an interactive, runnable API reference (e.g. a Swagger/try-it console); a direct probe for openapi.json/swagger.json on the docs site returned 404s, indicating no in-browser interactive reference exists.

   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Zulip~partialprobed5/10

   Zulip publishes a full machine-readable OpenAPI 3.0 spec for its REST API (zulip-probe-5) and a public API reference site with example endpoints like 'Send a message' (zulip-docs-5), and the API is confirmed live and functional hands-on (zulip-probe-4). However, there is no direct evidence that the API reference page itself offers interactive 'try it out' runnable examples in-browser rather than just documented curl/code snippets. Missing for 10: explicit confirmation of an in-browser interactive/try-it console on the API docs, independent user reports of using runnable examples.

   • [claimed-docs] “Send a message”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Zulip
   Slack~partialprobed6/10

   An official OpenAPI 2.0 spec for the Web API (and AsyncAPI spec for Events API) exists in the slackapi/slack-api-specs GitHub repo, satisfying the core ask of a machine-readable spec. However, live probes show the obvious/expected locations on docs.slack.dev (openapi.json, swagger.json, etc.) all 404, meaning the spec isn't directly downloadable from the primary docs site and requires knowing about a separate GitHub repo. Missing for 10: direct download link from docs.slack.dev, first-party documentation pointing users to the spec repo, and independent confirmation the spec is kept in sync with the live API.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”

   proof ↗⚑ flag

   Zulip✓fullprobed9/10

   Zulip's REST API ships a machine-readable OpenAPI 3.0.1 spec (zulip.yaml, ~1.5MB) directly in its repo, confirmed hands-on, and the live API docs at zulip.com/api/ are generated from this spec. Missing for 10: no dedicated discoverable download link/endpoint on the main docs site itself (openapi.json probes 404'd, so it's not trivially discoverable without knowing the GitHub path).

   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [claimed-docs] “Send a message”
   • [probe] “PROBE openapi: all candidate paths 404 (https://zulip.com/openapi.json, https://zulip.com/swagger.json, https://zulip.com/api/openapi.json, …”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Slack
   Slack✓fullclaimed7/10

   Slack's official docs describe a 'developer sandbox' as an Enterprise org environment explicitly built to let developers 'build against all Slack features safely and securely' and 'empower teams to build without putting production at risk,' directly matching the story of testing without touching production data. However, missing for 10: independent/hands-on confirmation of the sandbox in use, clarity on whether this is available outside Enterprise plans, and detail on how it isolates AI/agent-specific testing (e.g., MCP server or bot testing) within that sandbox.

   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”
   • [claimed-docs] “Empower teams to build without putting production at risk”

   proof ↗⚑ flag

   Zulip—none0/10

   The evidence pack covers self-hosting, export/import, integrations, and API access, but nowhere mentions a dedicated sandbox, staging, or test-mode instance that is separate from production data. Nothing describes a way to safely test bots/integrations against non-production data without standing up and fully configuring an entirely separate self-hosted server.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Slack
   Slack~partialclaimed6/10

   Slack maintains official OpenAPI specs for its Web API and a dated, running deprecation changelog with explicit migration windows (e.g., classic app deprecation date), which supports documented deprecation policy; the Web API and Events API references also show first-party API documentation. However, there's no explicit evidence of a formal API versioning scheme (e.g., v1/v2 endpoint versioning) beyond method-level docs and changelog dates. Missing for 10: explicit versioning scheme documentation, independent/community corroboration of deprecation practices being honored reliably.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “api.slack.com/changelog/deprecations is a running, dated log of API deprecation announcements with migration windows, e.g. "We'd like to upd…”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”

   proof ↗⚑ flag

   Zulip—none0/10

   While Zulip clearly has a documented, machine-readable REST API (OpenAPI spec, live endpoint, CLI) per zulip-docs-5, zulip-probe-4/5/6, the evidence pack contains no mention of API versioning scheme or a deprecation policy for changed/removed endpoints. Missing for 10: documentation of API version numbers, backward-compatibility guarantees, or a deprecation/changelog process.

   ⚑ flag

Apps

1. team-adminInstall prebuilt integrations from an app directory or marketplace

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack explicitly advertises an App Directory with 2,600+ prebuilt apps (Salesforce, Jira, Google Drive, ChatGPT, etc.) and a help doc specifically for admins on how to add apps to a workspace. This directly matches the team-admin persona and app-platform theme. missing for 10: independent/hands-on confirmation of the admin install/approval workflow beyond the docs, and no detail on admin-specific approval controls for directory apps (only MCP client approval is mentioned).

   • [claimed-docs] “Choose from over 2,600 apps in the Slack App Directory — from Salesforce, Jira, Google Drive, ChatGPT, and more.”
   • [claimed-docs] “Add apps to your Slack workspace”
   • [claimed-docs] “Connect, simplify, and automate. Discover the power of apps and tools.”

   proof ↗⚑ flag

   Zulip✓fullclaimed7/10

   Zulip provides an official integrations directory (zulip.com/integrations) listing 130+ native prebuilt integrations plus Zapier/IFTTT for hundreds more, which team-admins can browse and install/configure (e.g., via incoming webhooks) without custom coding. missing for 10: no evidence of an in-app 'install with one click' marketplace UI or independent hands-on confirmation of the install flow.

   • [claimed-docs] “Over 130 native integrations. And hundreds more through Zapier and IFTTT.”
   • [claimed-docs] “Over 130 native integrations.”
   • [claimed-docs] “Incoming webhooks”

   proof ↗⚑ flag

2. developerRegister custom slash commands that users invoke from the message box

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack covers Slack's general app-platform tooling (CLI, Bolt frameworks, Web/Events APIs, Block Kit, Workflow Builder, MCP server) but never mentions slash commands specifically as a registrable app feature invoked from the message box.

   ⚑ flag

   Zulip—none0/10

   Zulip's docs describe an interactive-bot framework that reacts to messages, but there is no evidence of a slash-command registration API or mechanism where a developer registers a custom command invoked via '/' in the message box, distinct from Slack-style slash commands.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”

   proof ↗⚑ flag

3. developerBuild apps with rich interactive UI inside chat — modals, buttons, and structured message layouts

   weight 2 · round to Slack
   Slack✓fullclaimed9/10

   Slack's Block Kit is explicitly documented as the JSON-based framework for building modals, messages, and tabs with the same building blocks, backed by chat.postMessage's structured 'blocks' parameter, plus SDKs (Bolt for Java/Python/JS, Node Slack SDK) and CLI tooling to build these apps. This directly matches the story of building rich interactive UI (modals, buttons, structured layouts) inside Slack chat. Missing for 10: no independent/hands-on developer corroboration of the Block Kit UI-building experience beyond first-party docs.

   • [claimed-docs] “Whether you're composing layouts for modals, messages, or tabs, the Block Kit building experience is the same — your app will be sculpting s…”
   • [claimed-docs] “A JSON-based array of structured blocks, presented as a URL-encoded string.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”

   proof ↗⚑ flag

   Zulip—none0/10

   Evidence covers Zulip's bot/API framework, integrations, and messaging features but contains no mention of interactive UI elements like modals, buttons, or structured message layouts within chat (unlike Slack's Block Kit or similar). Missing for 10: any documentation of interactive message components, modal dialogs, button widgets, or structured layout building blocks for developers.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Slack—none0/10

   Slack's Web API and MCP server document single-item actions (send one message, upload one file, create one list entry, etc.) with no documented batch/bulk endpoints or MCP tools for operating across many items in one call. Workflow Builder and automations are trigger-based, not bulk-operation mechanisms, and export tools are admin-only data dumps rather than AI-native bulk actions.

   ⚑ flag

   Zulip—none0/10

   While Zulip exposes a full REST API and CLI tooling (zulip-probe-5, zulip-probe-6, zulip-docs-5) that could theoretically be scripted, the evidence pack contains no documentation or hands-on proof of a bulk/batch endpoint (e.g., mass message updates, bulk channel management, batch subscribe/unsubscribe) that lets an AI-native user act on many items in one call. missing for 10: documented bulk-update/bulk-delete/batch endpoints, evidence of batch request support, any example of operating on multiple items in a single API call.

   • [claimed-docs] “Send a message”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Workflow Builder lets users define triggers, conditional branches, and webhook-based automations that fire actions on events (message posted, emoji reaction, webhook call, etc.), directly matching the story; the Events API further supports event-driven automation. missing for 10: independent/hands-on verification of workflow trigger reliability and no evidence of AI-native rule authoring beyond no-code builder.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”
   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”

   proof ↗⚑ flag

   Zulip~partialclaimed4/10

   Zulip has no documented native rules/automation engine; the closest capabilities are a bot framework requiring custom code (zulip-docs-4/12/24) and webhook/Zapier/IFTTT integrations (zulip-docs-9/19) that let external tools trigger actions on Zulip events. This is automation via third-party glue or coding, not a built-in 'define rules' feature. Missing for 10: a native no-code rules/trigger builder, first-party documentation of event-condition-action automation, and any evidence of it working out-of-the-box without external services or custom bot code.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Over 130 native integrations. And hundreds more through Zapier and IFTTT.”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Incoming webhooks”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Slack
   Slack~partialclaimed4/10

   Slack's Workflow Builder is documented as a no-code automation tool with webhook triggers and conditional branching, which are automation-depth building blocks, but the evidence never explicitly mentions a 'scheduled' or 'recurring' trigger type for jobs/workflows. AI-native automation is described mostly around single-shot chat/AI features (summaries, briefings) rather than recurring job scheduling. missing for 10: explicit documentation of scheduled/recurring trigger type in Workflow Builder, independent confirmation of recurring automation use, and any AI-agent-specific recurring job scheduling capability.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”

   proof ↗⚑ flag

   Zulip—none0/10

   Zulip is a team chat platform with bots, integrations, and an API for sending messages, but there is no evidence of any scheduler, cron-like feature, or recurring workflow/job automation capability — only reactive bots and one-off messages are documented.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [claimed-docs] “Send a message”

   proof ↗⚑ flag

Ai agents

1. ai-native userAdd an AI agent as a member of a channel that participates in conversations when mentioned

   weight 3 · round to Slack
   Slack✓fullclaimed7/10

   Slack's Events API lets bots/apps respond to activity in channels ('Slack calls you'), and its ecosystem explicitly supports adding AI agents like ChatGPT, Claude, and Slackbot as channel-integrated participants that act on mentions/requests (e.g. 'start using tools like ChatGPT, Claude... within your chats', 'Route work through Slackbot... routing requests to agents', 'Coding agents can now work with your whole team'). Combined with the CLI/Bolt SDKs for building bot apps that join channels, this shows the underlying capability is well supported. Missing for 10: explicit first-party documentation of the app_mention event/scope specifically triggering agent responses, and independent hands-on confirmation that a mentioned agent reliably replies in-channel.

   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “Coding agents can now work with your whole team, not just you.”
   • [claimed-docs] “Route work through Slackbot. Coordinate work by routing requests to agents and get results delivered right back into your workflow.”
   • [claimed-docs] “Easily connect agents, software, and all your apps in just a few clicks, and start using tools like ChatGPT, Claude, and Asana right within …”
   • [claimed-docs] “By connecting them to your conversations and data in Slack, agents like Agentforce, ChatGPT, Claude, Notion, Slackbot, and Writer become eve…”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Zulip~partialprobed6/10

   Zulip's documented bot framework lets you write and run custom bots (including via a dedicated Botserver for production) that 'react to messages,' and the full REST/API surface (confirmed live and via OpenAPI spec) supports sending/receiving messages, which is the technical substrate needed for an AI-agent-as-channel-member use case. However, this requires custom bot development rather than a first-party 'add an AI agent to a channel' feature, and there's no explicit documentation or evidence of native @-mention-triggered AI agent participation out of the box. Missing for 10: explicit first-party AI-agent bot support (vs generic bot framework), documentation of mention-triggered behavior specifically, and independent/hands-on confirmation of an AI agent actually participating in a channel conversation.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”

   proof ↗⚑ flag

2. ai-native userHave an agent read and post channel messages through the official API using scoped tokens

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's official Web API (chat.postMessage, chat.history-type methods via OpenAPI spec covering user/bot token usage) plus scoped OAuth tokens is well documented, enabling agents to read and post channel messages programmatically; the MCP server and SDKs (Bolt, node-slack-sdk) further formalize agent access with admin-approved scopes. missing for 10: no independent hands-on developer report confirming real-world token-scoping friction or reliability at scale, and no explicit doc excerpt enumerating channel-read scopes (e.g., channels:history) alongside chat:write in one place.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”

   proof ↗⚑ flag

   Zulip✓fullprobed7/10

   Zulip ships a documented, versioned REST API (OpenAPI spec, live endpoint confirmed) with a bot framework specifically designed to read and react to channel messages and a documented message-sending endpoint, plus an official CLI/Python client for scripting — bots authenticate via their own per-bot API key, which functions as a scoped credential distinct from a user's. missing for 10: explicit documentation of granular token scopes/permissions (vs. just per-bot keys), and an explicit documented 'read messages' endpoint (only send-message and bot-reacts-to-message are directly evidenced).

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Send a message”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

Bot api

1. developerPost a message into a channel with a simple incoming webhook URL

   weight 2 · round to Zulip
   Slack~partialclaimed5/10

   Slack's docs evidence shows webhook-based triggers for Workflow Builder ("how to start a workflow from outside of Slack") and the chat.postMessage Web API method for sending messages, both of which can be used to post into a channel from an external system, but neither is the classic single-URL 'Incoming Webhook' integration developers commonly expect. Missing for 10: explicit documentation of the dedicated Incoming Webhooks app/URL for zero-config posting, and any hands-on confirmation that a bare webhook POST (without workflow setup or OAuth token) posts a message.

   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”

   proof ↗⚑ flag

   Zulip✓fullprobed8/10

   Zulip explicitly documents incoming webhooks as a native integration type (zulip-docs-19) alongside 130+ native integrations (zulip-docs-9/13), and its API includes a straightforward 'send a message' endpoint (zulip-docs-5) backed by a full OpenAPI spec (zulip-probe-5) and live-verified API (zulip-probe-4). This matches the standard incoming-webhook-posts-to-channel pattern. Missing for 10: a first-party doc snippet showing the exact incoming-webhook URL format/config screen, and independent third-party confirmation of webhook setup ease.

   • [claimed-docs] “Incoming webhooks”
   • [claimed-docs] “Over 130 native integrations. And hundreds more through Zapier and IFTTT.”
   • [claimed-docs] “Send a message”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”

   proof ↗⚑ flag

2. developerBuild a bot that receives messages and events in real time through an events API or gateway connection

   weight 3 · round to Slack
   Slack✓fullclaimed9/10

   Slack's Events API is explicitly documented to push real-time events to developer-built apps/bots via HTTP endpoint or Socket Mode, with subscription filtering, and this is complemented by SDKs (Bolt for Java, Node SDK) and quickstart guides for building bots. Missing for 10: independent hands-on developer corroboration of reliability/latency of the events pipeline beyond first-party docs.

   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Zulip✓fullprobed7/10

   Zulip explicitly documents a bot framework that lets developers write custom bots that 'react to messages in Zulip' in real time, deployable persistently via the Zulip Botserver, backed by a full OpenAPI-documented REST API and a working live API endpoint plus an installable CLI/client library for scripting integrations. This maps to Zulip's known events/register API model for real-time bots, though the evidence pack never names the events/register endpoints or long-polling mechanics explicitly. Missing for 10: explicit documentation/citation of the events/register API endpoints and real-time event queue mechanics, and independent hands-on confirmation of a bot actually receiving live events.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

Ai notes

1. ai-native userGet AI-generated notes and recaps from meetings and huddles I attended or missed

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's docs directly claim AI note-taking for huddles (key takeaways, action items, who said what compiled at huddle end) and AI-generated channel/thread summaries and daily recaps for content missed, matching the story's core ask. Missing for 10: independent/hands-on corroboration of huddle-note accuracy or completeness, and no explicit confirmation that recaps cover 'missed' meetings specifically (recaps are framed around channels/threads more than scheduled meetings).

   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Create time-saving automations in a few clicks, translate conversations into any language, and even use AI to take meeting notes.”
   • [claimed-docs] “translate conversations into any language, and even use AI to take meeting notes”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack. Any links, documents, and messages shared during a huddle are automatically saved once the …”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack.”

   proof ↗⚑ flag

   Zulip—none0/10

   No evidence of any meeting/huddle recording, transcription, or AI-generated recap/notes feature; Zulip's evidence covers topics, channels, bots, integrations, and self-hosting but nothing about calls, huddles, or AI summarization of conversations.

   ⚑ flag

Calls

1. team-adminStart an audio or video call directly from a channel or DM without leaving the app

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Huddles feature lets any user click the headphones icon in a channel/DM header to instantly start audio or video calls with screen sharing, all inside the app, and includes admin-manageable extras like AI notes and saved shared content. missing for 10: no explicit documentation of admin-specific controls/permissions for enabling or restricting huddles, and no independent hands-on corroboration beyond Slack's own marketing docs.

   • [claimed-docs] “Simply click on the headphones icon in the conversation header to start a huddle with your team.”
   • [claimed-docs] “Huddles happen right in Slack. Instantly connect over audio or video and share screens so you can get more done where you're already working…”
   • [claimed-docs] “Bring the feeling of working side-by-side to a virtual space that lets you collaborate and co-create live.”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack. Any links, documents, and messages shared during a huddle are automatically saved once the …”
   • [claimed-docs] “Emoji reactions. Colorful backgrounds. Delightful effects. In huddles, teams can express themselves to make being together even better.”

   proof ↗⚑ flag

   Zulip—none0/10

   No evidence in the pack mentions audio/video calling features in Zulip; all documentation and community references cover topics, channels, search, bots, integrations, export/import, and self-hosting, but nothing about starting a call from a channel or DM.

   ⚑ flag

External collaboration

1. team-adminCollaborate with external partners through guest accounts or shared channels with limited access

   weight 2 · round to Zulip
   Slack—none0/10

   The evidence pack contains no mention of guest accounts, Slack Connect, or shared/external channels with limited access — nothing about admin controls for external collaboration appears anywhere in the docs, community, or probe items. This is a mainstream, applicable capability for a workspace chat product, but absence of evidence means it cannot be credited.

   ⚑ flag

   Zulip~partialclaimed3/10

   Zulip docs mention that 'guests' are a distinct role with restricted channel subscription ability (zulip-docs-22), implying a guest-account mechanism exists, but the evidence pack contains no documentation of inviting external partners, guest account setup/permissions, or any shared-channel/cross-organization collaboration feature. Missing for 10: explicit guest-invite workflow docs, permission scoping details for guests, and any shared-channel-with-external-org capability or independent confirmation it works in practice.

   • [claimed-docs] “Everyone other than guests can subscribe to any public or web-public channel.”

   proof ↗⚑ flag

Messaging model

1. team-adminOrganize conversations into public and private channels with membership controls

   weight 3 · round to Zulip
   Slack—none0/10

   The evidence pack focuses almost entirely on Slack's AI/MCP tooling, developer SDKs, huddles, and integrations, with no first-party documentation describing channel creation, public vs. private channel types, or admin membership controls. The only channel-related mentions (e.g., MCP 'search channels', a raw SEO keyword list) do not document this admin capability.

   ⚑ flag

   Zulip~partialclaimed6/10

   Docs confirm channels can be public/private/web-public with subscription controls (zulip-docs-2, zulip-docs-22), and channel-scoped search/export tools acknowledge private channel membership boundaries (zulip-docs-14, zulip-docs-17). However, there is no explicit documentation of admin-side membership management workflows (adding/removing members, role-based permissions per channel) or granular channel permission settings. missing for 10: detailed admin UI/API for managing channel membership and permissions, evidence of private channel invite-only enforcement, independent corroboration of admin controls in practice.

   • [claimed-docs] “Subscribing to a channel makes conversations in that channel appear in your inbox, recent conversations, combined feed and left sidebar.”
   • [claimed-docs] “Everyone other than guests can subscribe to any public or web-public channel.”
   • [claimed-docs] “Public and private data (with consent): Everything in the export of public data, plus all the private channel messages and direct messages t…”
   • [claimed-docs] “channels:public: Search messages in all public and web-public channels.”

   proof ↗⚑ flag

2. team-adminReply in threads so side discussions stay attached to the original message

   weight 3 · round to Zulip
   Slack~partialcommunity3/10

   No first-party Slack documentation in this evidence pack describes the threading/reply feature directly; the only evidence that threads exist comes from community complaints (comm-12, comm-14) confirming the feature is used but describing it as poorly notified, hard to find replies, and 'close to impossible to use' as a tiny side panel with missing capabilities (snippets/files/slash commands not working in threads). This suggests threads function but with real UX friction, not a clean full delivery. Missing for 10: official docs/screenshots describing thread-reply UX, independent confirmation that reply notifications and thread views work smoothly, and resolution of the cited usability complaints.

   • [community] “My biggest pain point is Slack's awful implementation of threads - you only get notified of new thread replies in a 'New Threads' view that …”
   • [community] “Zulip is a very good fit for open source communities, and much much better for communication than Slack. Slack encourages saying everything …”

   proof ↗⚑ flag

   Zulip✓fullcommunity8/10

   Zulip's core topic-based threading model lets users reply within a topic to keep side discussions attached to the original conversation, and community evidence strongly corroborates this as a standout feature ('the killer feature', 'fundamentally superior model' to Slack threads). Docs describe starting/joining topics and searching within them, and admins have the same messaging capabilities as any user. missing for 10: explicit admin-specific documentation on replying in threads (evidence is general-user focused), and some community reports note UX friction/confusion for non-technical users when threading.

   • [claimed-docs] “To get the full benefits of Zulip's topic model, when starting a new conversation, you should start a new topic!”
   • [claimed-docs] “Lots of conversations can happen in the same channel at the same time, each in its own topic. You never have to worry about interrupting — e…”
   • [claimed-docs] “Click the start a new topic () button next to the name of the channel where you’d like to start a conversation.”
   • [community] “The 'threaded' part is key here. Slack threads are useless compared to Zulip. In Zulip you can create threads on the fly from existing messa…”
   • [community] “Threads are one major reason I like Zulip over Slack, but speed is another... For some reason when I use Slack, the keys feel mushy.”
   • [community] “I used Zulip while at Akamai... My experience was so positive that I've continued to evangelize it at other companies since then... The most…”
   • [community] “I use Zulip all the time at work. It is ugly, sometimes will post to a different thread than you expect... has an infuriating tick that if y…”

   proof ↗⚑ flag

3. team-adminCatch up on busy channels efficiently because every conversation is organized under a named topic or thread

   weight 2 · round to Zulip
   Slack!disputedcontradicted5/10

   Slack does support channel/thread organization plus AI features to summarize channels and threads for catching up (slack-docs-15, slack-docs-19, slack-docs-34), but concrete hands-on community reports say the thread implementation itself is poorly organized and hard to use — notifications don't auto-update, threads are 'a tiny section off to the side,' and Slack 'encourages saying everything in the main channel' rather than threads (slack-comm-12, slack-comm-14). This directly contradicts the premise that conversations are cleanly organized under threads for efficient catch-up. Missing for 10: independent verification that threading/summarization actually resolves the catch-up problem in practice, admin-specific tooling for enforcing thread discipline.

   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [community] “My biggest pain point is Slack's awful implementation of threads - you only get notified of new thread replies in a 'New Threads' view that …”
   • [community] “Zulip is a very good fit for open source communities, and much much better for communication than Slack. Slack encourages saying everything …”

   proof ↗⚑ flag

   Zulip✓fullcommunity8/10

   Zulip's topic model is core to the product: docs explain starting new topics per conversation, subscribing to channels surfaces conversations in inbox/feed, and topic-scoped search lets admins filter busy channels. Community reports strongly corroborate that this threading model is 'fundamentally superior' to Slack for following busy, high-volume discussions without being overwhelmed, and the 'all messages' view helps catch up chronologically across channels. Missing for 10: independent measurement of catch-up efficiency and some community reports note UX friction (miscasting to wrong topic, non-technical user confusion) that slightly tempers the ideal experience.

   • [claimed-docs] “To get the full benefits of Zulip's topic model, when starting a new conversation, you should start a new topic!”
   • [claimed-docs] “Subscribing to a channel makes conversations in that channel appear in your inbox, recent conversations, combined feed and left sidebar.”
   • [claimed-docs] “channel:design has:image new logo: Search for messages in #design that include an image and contain the keywords new and logo.”
   • [claimed-docs] “Lots of conversations can happen in the same channel at the same time, each in its own topic. You never have to worry about interrupting — e…”
   • [claimed-docs] “Click the start a new topic () button next to the name of the channel where you’d like to start a conversation.”
   • [community] “We've been using Zulip internally for a couple of years now... It lets us have real, ongoing, and substantive conversations with a large num…”
   • [community] “The 'threaded' part is key here. Slack threads are useless compared to Zulip. In Zulip you can create threads on the fly from existing messa…”
   • [community] “We used Zulip (then a commercial product) at FoundationDB, and really liked it... the killer feature is the 'all messages' view that merges …”
   • [community] “I used Zulip while at Akamai... My experience was so positive that I've continued to evangelize it at other companies since then... The most…”
   • [community] “I use Zulip all the time at work. It is ugly, sometimes will post to a different thread than you expect... has an infuriating tick that if y…”
   • [community] “Zulip seemed like technically the most polished product... what ended up being the showstopper was that new users were very confused about h…”

   proof ↗⚑ flag

Notifications

1. team-adminTune notifications per channel, keyword, and schedule so only what matters interrupts me

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack contains no documentation on per-channel/keyword/schedule notification preferences (e.g., mute channels, keyword alerts, do-not-disturb scheduling) — Slack's actual notification settings are not represented anywhere in this pack, only unrelated AI, workflow, MCP, and integration docs. Missing for 10: any mention of notification preferences, keyword alerts, per-channel mute/schedule controls, or admin-level notification policy tools.

   ⚑ flag

   Zulip—none0/10

   The evidence pack contains no documentation or mentions of per-channel, per-keyword, or scheduled notification controls (e.g., no citations about notification settings, alert words, or do-not-disturb/quiet hours) — only topics, channels, search, bots, and export/import material. Notification tuning is a standard, fair axis for a chat product, but nothing in the pack demonstrates it.

   ⚑ flag

Compliance

1. platform-engineerReview audit logs of admin and user actions across the workspace

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack includes only workspace data export/import documentation (e.g., slack-docs-22/23/35/36) and community complaints about export restrictions (slack-comm-2), but nothing that documents an audit log capability tracking admin and user actions across the workspace. This is a fair and applicable axis for an enterprise collaboration platform, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”

   proof ↗⚑ flag

   Zulip—none0/10

   No evidence pack items mention audit logs, admin action logs, or user activity tracking features in Zulip; the evidence covers topics, channels, search, bots, integrations, and export/import tools but nothing about auditability of admin/user actions.

   ⚑ flag

2. platform-engineerEnforce message retention policies and legal holds for compliance and eDiscovery

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack shows generic data export/import guides (slack-docs-22/23/35/36) and a community note that Corporate Export requires legal/compliance justification and Slack approval (slack-comm-2), but nothing documents actual retention-policy enforcement, legal-hold placement, or eDiscovery tooling. Missing for 10: retention policy configuration, legal hold mechanism, eDiscovery search/export APIs, admin documentation on compliance holds.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”

   proof ↗⚑ flag

   Zulip—none0/10

   The evidence pack only covers data export/import tools for migrating organizations, with no mention of configurable message retention policies, automatic deletion schedules, or legal hold/eDiscovery preservation features. No documentation or community evidence addresses compliance-driven retention enforcement.

   ⚑ flag

Exports

1. team-adminExport the full message history of my workspace in machine-readable formats, including private conversations where policy allows

   weight 3 · round to Zulip
   Slack!disputedcontradicted5/10

   Slack does document official export tools for workspace data (slack-docs-22/23/35/36), which nominally support the compliance-export story, but community evidence directly contradicts free/easy access: Corporate Export of DMs and private channels requires legal/compliance justification and Slack's approval, and users questioned whether migrating years of full message history out of Slack is even feasible under these restrictions. Missing for 10: no first-party documentation of a machine-readable format spec (JSON/CSV schema details), no evidence addressing the approval-gate friction, and no independent confirmation that large-scale/private-channel exports actually work in practice.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”

   proof ↗⚑ flag

   Zulip✓fullclaimed8/10

   Zulip's docs explicitly describe an export tool that can include 'public and private data (with consent)' — private channel messages and DMs from consenting members — in a machine-readable export format used for migration/backup, directly matching the compliance-export story for a team-admin. This is corroborated by general export/import documentation and self-hosting docs confirming full data portability. Missing for 10: independent/hands-on verification of the export tool's exact output format and confirmation of admin-level override for private data without member consent.

   • [claimed-docs] “Zulip has high quality export tools that can be used to migrate between the hosted Zulip Cloud service and your own servers.”
   • [claimed-docs] “Public and private data (with consent): Everything in the export of public data, plus all the private channel messages and direct messages t…”
   • [claimed-docs] “You can move freely between Zulip Cloud hosting and your own servers with our high quality export and import tools.”
   • [claimed-docs] “To import data from Slack, Mattermost, Rocket.Chat, Zulip Cloud, or another Zulip server, follow the linked instructions.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Zulip
   Slack~partialprobed6/10

   Slack ships an extensive Web API (200+ methods per slack-docs-74), an Events API, official OpenAPI/AsyncAPI specs (slack-supp-openapi-spec), a CLI, SDKs, and an MCP server covering messaging, search, canvases, lists, and file uploads (slack-docs-8, slack-docs-28-30, slack-docs-48). However, community evidence shows a concrete gap: exporting DMs and private channel content requires legal/compliance justification and Slack approval, not open self-serve API access (slack-comm-2, slack-comm-4), and moderation tooling is described as 'purposefully useless' compared to UI expectations (slack-comm-9). Missing for 10: verified parity for admin/compliance-only UI actions (e.g., full data export, moderation controls) via API, and a public discoverable OpenAPI schema (probe shows standard openapi.json paths 404, slack-probe-2).

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Sends a message to a channel.”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”
   • [community] “I think 'less capable moderation tools' really undersells how purposefully useless and nonexistent Slack's moderation tools are for open com…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Zulip~partialprobed7/10

   Zulip ships a large, machine-readable OpenAPI spec (~1.5MB) covering messaging, bots, integrations, and administration, with a live public endpoint confirming the API works and an official CLI/bot framework for scripting (zulip-probe-5, zulip-probe-4, zulip-probe-6, zulip-docs-5, zulip-docs-12). However, there is no explicit vendor or independent claim that every UI action (e.g., search filters, topic management UI nuances) has a 1:1 API equivalent. Missing for 10: explicit UI-API parity documentation/audit, independent confirmation that all UI-only features (e.g., advanced search UX, settings toggles) are scriptable via API.

   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”
   • [claimed-docs] “Send a message”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Zulip
   Slack!disputedcontradicted4/10

   Slack documents a workspace data export feature (slack-docs-22/23/35/36), but concrete community evidence shows this is heavily restricted in practice: Corporate Export of DMs/private channels requires legal/compliance justification and Slack's approval (slack-comm-2), users openly question whether multi-year history can even be exported (slack-comm-4), and Slack has shut down open-protocol (IRC/XMPP) access that once enabled third-party/portable access (slack-comm-11). There's no evidence the export format is genuinely open/interoperable rather than a locked-down archive. Missing for 10: documented open export format specification, independent confirmation of unrestricted self-service export, and no contradicting reports of approval gating.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”
   • [community] “Slack decided to close down IRC and XMPP gateways, ending third-party client access via open protocols; the IRC gateway was the only thing t…”

   proof ↗⚑ flag

   Zulip✓fullcommunity8/10

   Zulip documents high-quality export tools that let users take both public and private (consented) data out in open formats, explicitly for migrating away from Zulip Cloud to self-hosted servers, and is fully open-source/self-hostable so no vendor lock-in exists. This directly matches 'export data and leave.' Missing for 10: no independent/hands-on verification of the export file format's openness or completeness, and no community testimonial specifically confirming a successful full data exodus.

   • [claimed-docs] “Zulip has high quality export tools that can be used to migrate between the hosted Zulip Cloud service and your own servers.”
   • [claimed-docs] “You can move freely between Zulip Cloud hosting and your own servers with our high quality export and import tools.”
   • [claimed-docs] “Public and private data (with consent): Everything in the export of public data, plus all the private channel messages and direct messages t…”
   • [claimed-docs] “When you self-host Zulip, you get the same software as our Zulip Cloud customers.”
   • [community] “Zulip is my favorite modern chat program because it's actually 100% FOSS, unlike Mattermost and RocketChat, which are only 'open core'.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Zulip
   Slack—none0/10

   Slack is closed-source proprietary SaaS; no evidence of any open-licensed source code release. Its CLI, MCP server, and APIs are tools around a closed core, not the product's source itself.

   ⚑ flag

   Zulip✓fullcommunity8/10

   Zulip's source code is hosted publicly on GitHub with a contributing guide, and Zulip is widely documented (including in community evidence) as being fully open-source (100% FOSS, not open-core), consistent with its known Apache 2.0 licensing. Missing for 10: explicit citation of the license file/text itself and independent third-party confirmation of the specific license terms.

   • [github] “Contributing code. Check out our guide for new contributors to get started.”
   • [community] “Zulip is my favorite modern chat program because it's actually 100% FOSS, unlike Mattermost and RocketChat, which are only 'open core'.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Zulip
   Slack—none0/10

   Slack is a cloud SaaS product; the evidence pack shows only hosted/cloud offerings, developer sandboxes, CLI, SDKs, and export tools—no self-hosted deployment option is documented anywhere, and community evidence even discusses difficulty exporting data or migrating off Slack's hosted service.

   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”
   • [claimed-docs] “A developer sandbox is an Enterprise org environment ... that can be used to build against all Slack features safely and securely, without a…”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”

   proof ↗⚑ flag

   Zulip~partialcommunity7/10

   Zulip is documented as fully open-source and self-hostable, with official production install docs, import/export tools to migrate between cloud and self-host, and a GitHub repo for contributing (zulip-docs-8, zulip-docs-25, zulip-docs-7, zulip-gh-1). However, community hands-on reports describe real friction: installs require a dedicated server/VM with poor containerization support, heavy RAM requirements, and limited distro support beyond Ubuntu (zulip-comm-18, zulip-comm-13, zulip-comm-14, zulip-comm-3). Missing for 10: independent verification that installation friction has been resolved, broader OS/container support, and clearer resource-requirement documentation.

   • [claimed-docs] “When you self-host Zulip, you get the same software as our Zulip Cloud customers.”
   • [claimed-docs] “install a self-hosted Zulip server on a system of your choice”
   • [claimed-docs] “To import data from Slack, Mattermost, Rocket.Chat, Zulip Cloud, or another Zulip server, follow the linked instructions.”
   • [claimed-docs] “Then, run the installer, providing your email address and the public hostname that users will be able to access your server with”
   • [github] “Contributing code. Check out our guide for new contributors to get started.”
   • [community] “On the downside, if you are self-hosting, Zulip requires a dedicated server (or VM). There are some efforts to make it run in a container bu…”
   • [community] “I love Zulip... what Zulip lacks right now is polish. Server installation for example is a mess. You basically need a dedicated Debian machi…”
   • [community] “The install procedure looks like a bad joke. So if I'm using RHEL, Fedora, Arch or any other Linux distribution, tough luck. If they're supp…”
   • [community] “Something has gone horribly wrong when a chat server can barely run on 2G... recommended 4GB of RAM for production use.”

   proof ↗⚑ flag

Pricing

1. team-adminKeep my team on a free tier without losing access to older message history

   weight 2 · round to Slack
   Slack!disputedcontradicted4/10

   Slack marketing claims 'Unlimited message history' (slack-docs-43), but this benefit is documented on the pricing page and is know to apply to paid tiers, and multiple community reports concretely describe free workspaces having message/storage limits enforced, with older messages disappearing once a few thousand messages are exceeded (slack-comm-10, slack-comm-15). This directly contradicts the idea that a team-admin can stay on a free tier indefinitely without losing history. Missing for 10: an explicit first-party statement about free-tier retention limits, and any first-party pricing-page confirmation that free tier does NOT purge history.

   • [claimed-docs] “Unlimited message history Every message, file, and conversation shared in Slack is saved and fully searchable.”
   • [community] “So much information that would reduce support burdens is buried in Slacks and Discords. It can't be found through Google, and if you aren't …”
   • [community] “I have like 7 Slacks, 2 paid and 5 hobby ones I use once a month. Slack pushing storage/message limits on free workspaces feels like a tiny …”

   proof ↗⚑ flag

   Zulip—none0/10

   The evidence pack contains no mention of Zulip's free-tier message history limits or retention policy, so there is no support for the claim that a free-tier team retains full access to older messages. Missing for 10: any documentation or community evidence about free-plan message history caps/retention, and confirmation that free tier does not truncate history.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Zulip
   Slack—none0/10

   No evidence in the pack mentions data residency, regional storage options, or geographic data controls for Slack; the evidence covers MCP servers, APIs, workflows, and AI features but nothing about choosing where data is stored. This is a fair axis for an enterprise SaaS product, but absence of evidence means it cannot be credited.

   ⚑ flag

   Zulip~partialclaimed6/10

   Zulip's self-hosting docs let users install the server 'on a system of your choice' anywhere they want, effectively giving control over data location/residency, and full export/import tools support migrating data between Zulip Cloud and self-hosted servers. However, there is no evidence of a built-in region-selection feature within Zulip Cloud itself (e.g., choosing EU vs US data centers) — the only residency mechanism is self-hosting your own infrastructure. Missing for 10: explicit multi-region hosting options within Zulip Cloud, documented data-residency guarantees, and independent confirmation of regional deployment support.

   • [claimed-docs] “When you self-host Zulip, you get the same software as our Zulip Cloud customers.”
   • [claimed-docs] “install a self-hosted Zulip server on a system of your choice”
   • [claimed-docs] “Zulip has high quality export tools that can be used to migrate between the hosted Zulip Cloud service and your own servers.”
   • [claimed-docs] “You can move freely between Zulip Cloud hosting and your own servers with our high quality export and import tools.”
   • [claimed-docs] “Then, run the installer, providing your email address and the public hostname that users will be able to access your server with”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Slack—none0/10

   No evidence in the pack addresses AI training data opt-out or controls preventing Slack/customer data from being used to train AI models; the pack covers unrelated AI features (search, summarization, MCP server) and export/pricing controversies but nothing about AI-training data usage or opt-out settings.

   ⚑ flag

   Zulip—none0/10

   No evidence in the pack addresses AI training data usage, opt-out controls, or any explicit AI-training privacy policy for Zulip; self-hosting is mentioned but not tied to preventing AI training use of data. missing for 10: explicit policy/statement on AI model training use of data, opt-out mechanism, or contractual guarantee against training use.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Zulip
   Slack!disputedcontradicted3/10

   Slack documents workspace export/import tools (data retention/deletion-adjacent controls), but community evidence explicitly says business customers can't freely export their own chats — Corporate Export requires legal/compliance justification and Slack's approval, and even feasibility of full history export is questioned. This directly contradicts the notion of straightforward user/admin control over data retention and deletion. Missing for 10: explicit documentation of configurable retention periods, deletion policies/workflows, and independent confirmation that exports/deletions can be self-served without gatekeeping.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”

   proof ↗⚑ flag

   Zulip~partialclaimed4/10

   Zulip's self-hosting option and data export/import tools (including exporting private data with consent) give users significant control over where their data lives and how it can be extracted or migrated, which touches on data retention/portability. However, there is no direct evidence of message retention policies, auto-deletion settings, or a documented data-deletion workflow for accounts/messages. Missing for 10: explicit retention-policy controls, message/account deletion documentation, and any GDPR-style data-deletion API or admin setting.

   • [claimed-docs] “Zulip has high quality export tools that can be used to migrate between the hosted Zulip Cloud service and your own servers.”
   • [claimed-docs] “You can move freely between Zulip Cloud hosting and your own servers with our high quality export and import tools.”
   • [claimed-docs] “Public and private data (with consent): Everything in the export of public data, plus all the private channel messages and direct messages t…”
   • [claimed-docs] “When you self-host Zulip, you get the same software as our Zulip Cloud customers.”
   • [claimed-docs] “install a self-hosted Zulip server on a system of your choice”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Slack—none0/10

   No evidence in the pack addresses telemetry or usage-tracking opt-out controls for Slack; the privacy/data-export items (slack-comm-2, slack-docs-22/23/35/36) relate to data export/retention, not telemetry opt-out. This axis plausibly applies to a SaaS collaboration product, but no supporting capability is documented.

   ⚑ flag

   Zulip—none0/10

   No evidence in the pack addresses telemetry, usage tracking, analytics collection, or an opt-out setting for Zulip; the self-hosting docs discuss data export/import and deployment but never mention telemetry controls.

   ⚑ flag

Ai catchup

1. ai-native userGet AI-generated summaries and recaps of channels and threads I missed

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's first-party AI features docs explicitly state AI in Slack can summarize channels and threads and serve daily recaps (slack-docs-15), backed by Slackbot as an intelligent daily briefing/agent (slack-docs-13, slack-docs-14) and huddle note-taking/recaps (slack-docs-19, slack-docs-34). This directly matches the story of AI-generated summaries/recaps of missed channels/threads. Missing for 10: independent/hands-on verification of summary quality or accuracy, and no community evidence corroborating real-world reliability of this specific feature (community evidence pack focuses on unrelated pain points like pricing/export/threads UX).

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”

   proof ↗⚑ flag

   Zulip—none0/10

   No evidence of any AI-generated summary, recap, or digest feature for missed channels/threads; documentation focuses on topics, search, bots, integrations, and export/import but never mentions AI summarization.

   ⚑ flag

Search

1. team-adminSearch the full message history with filters like sender, channel, and date

   weight 3 · round drawn
   Slack~partialclaimed6/10

   Slack docs confirm full, unlimited searchable message history (slack-docs-43, slack-docs-16/52) and Slack's native search supports filtering, but the evidence pack does not explicitly document admin-specific advanced search operators (from:, in:, before:/after:) or an admin-console-level cross-workspace search UI beyond general user search claims; the MCP server also offers 'searching through Slack' but is a separate API-driven tool rather than the admin search UI itself. missing for 10: explicit documentation of native in-app search filter syntax (sender/channel/date), evidence of admin-level search scope (e.g. Enterprise-wide search across workspaces), and independent/hands-on confirmation of filter functionality.

   • [claimed-docs] “Unlimited message history Every message, file, and conversation shared in Slack is saved and fully searchable.”
   • [claimed-docs] “Conversations with coworkers, PDFs, images for your social campaign, decks buried in Google Drive, support tickets, customer records from Sa…”
   • [claimed-docs] “if it's shared in or integrated into Slack, it's searchable.”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”

   proof ↗⚑ flag

   Zulip~partialcommunity6/10

   Zulip's docs confirm a full-text search with real filter syntax (channel:design, has:image, channels:public) and state it offers 'a wide array of search filters', but the evidence pack never shows explicit sender: or date-range filter syntax, and one community report from 2016 claims the search function 'barely works'. missing for 10: explicit sender: and date/time filter documentation, independent verification of search accuracy, resolution of the community complaint about search reliability.

   • [claimed-docs] “channel:design has:image new logo: Search for messages in #design that include an image and contain the keywords new and logo.”
   • [claimed-docs] “channels:public: Search messages in all public and web-public channels.”
   • [claimed-docs] “Zulip also offers a wide array of search filters, which can be used on their own, or in combination with keywords.”
   • [community] “I love Zulip... what Zulip lacks right now is polish. Server installation for example is a mess. You basically need a dedicated Debian machi…”

   proof ↗⚑ flag

Workflow builder

1. team-adminBuild no-code workflows triggered by events, schedules, or form submissions inside the chat tool

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Workflow Builder is documented as a no-code way to build workflows directly in Slack, supporting event/schedule/form-submission triggers, webhook triggers, and conditional branching. missing for 10: independent/hands-on corroboration of the builder in use, and detail on schedule-based triggers specifically beyond webhook/event mentions.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”

   proof ↗⚑ flag

   Zulip—none0/10

   Zulip's evidence shows only custom-coded bots, webhooks, and 130+ integrations plus optional Zapier/IFTTT connections (external tools), but no built-in no-code workflow/automation builder with triggers, schedules, or form submissions inside the chat product itself.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Over 130 native integrations. And hundreds more through Zapier and IFTTT.”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Incoming webhooks”

   proof ↗⚑ flag