Discord vs Zulip
Discord
Discord Inc.
Zulip wins · 8–14 (20 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to DiscordDirect probe evidence confirms Discord's developer docs serve a working llms.txt (HTTP 200) with an index of documentation pages, and individual doc pages are also available in .md format explicitly for agent consumption, pointing back to the llms.txt index. Missing for 10: no independent third-party confirmation of agent usage/adoption beyond the probe itself.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.discord.com/llms.txt # Documentation - Discord - [Discord Developer Platform](https://docs.discord…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.discord.com/developers/intro.md > ## Documentation Index > Fetch the complete documentation index at…”
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…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnDiscord's REST API, bot tokens, and webhooks are explicitly documented as usable without a GUI, including a direct example of 'CI/CD pipelines posting build results or deployment notifications' via webhooks, and bots can run headlessly against the Gateway/REST API using only a token. However there's no first-party CLI, headless test harness, or SDK-level guidance for running the whole platform in automated pipelines beyond webhooks/bots. Missing for 10: an official CLI or headless client mode, dedicated CI documentation/examples beyond webhooks, and independent confirmation of headless bot reliability in CI.
- [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
- [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
- [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
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…”
ai-native userDrive the product through a documented public API
weight 3 · round to ZulipDiscord provides a well-documented REST API, Gateway WebSocket API, OAuth2, bot tokens, webhooks, and slash commands — all extensively documented for programmatic/AI-driven access (discord-docs-35, -10, -4, -5, -7). This gives an AI-native user a clear documented public API surface to drive the product. Missing for 10: no discoverable OpenAPI/Swagger spec (probe confirms 404s at standard paths), and no independent third-party verification of API completeness beyond first-party docs.
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
- [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.discord.com/openapi.json, https://docs.discord.com/swagger.json, https://docs.discord.c…”
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…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to DiscordDiscord's API supports OAuth2 bearer tokens with defined scopes and bot tokens with granular permission bits (docs-4, docs-6, docs-17, docs-18, docs-27), which technically allow issuing narrower-than-full-access credentials for any integration, including an agent. However, there is no documentation framing this specifically for AI agents or describing least-privilege credential issuance workflows tailored to autonomous/agentic use. missing for 10: agent-specific scoped-credential guidance, examples of least-privilege bot/OAuth setups for AI agents, independent confirmation of scope granularity in practice.
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “The first step in implementing OAuth2 is registering a developer application and retrieving your client ID and client secret.”
- [claimed-docs] “Using a bot token found on the Bot page within your app’s settings... Using an OAuth2 bearer token gained through the OAuth2 API.”
- [claimed-docs] “OAuth2 enables application developers to build applications that utilize authentication and data from the Discord API.”
- [claimed-docs] “allows /users/@me/connections to return linked third-party accounts”
Zulipnone0/10Zulip 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”
ai-native userBuild against official SDKs
weight 2 · round drawnDiscord provides extensive first-party documentation for building against official SDKs and APIs — the REST API, Gateway (WebSocket) API, OAuth2, Embedded App SDK, and a full Discord Social SDK with platform-specific guides for Unity, Unreal Engine, C++, iOS/Android, and web/mobile account linking. This gives builders (including AI-native developers) clear, well-documented interfaces to build bots, apps, and integrations. Missing for 10: independent/hands-on developer corroboration of SDK integration experience and AI-agent-specific SDK examples or tooling.
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “Our Embedded App SDK makes it quick and easy to ship native web apps, games, and interactive experiences.”
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
- [claimed-docs] “allowing them to connect with their friends and communities on Discord without leaving your game”
- [claimed-docs] “This guide will walk you through integrating the Discord Social SDK into a Unity project.”
- [claimed-docs] “Get started with the Discord Social SDK in C++ applications.”
- [claimed-docs] “Integrate the Discord Social SDK into Unreal Engine games.”
- [claimed-docs] “With the Discord Social SDK, you can offer a seamless social experience for your players, allowing them to connect with their friends and co…”
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”
ai-native userSubscribe to events via webhooks
weight 2 · round to DiscordDiscord's webhook docs explicitly state apps can 'receive event notifications from Discord delivered to your app over HTTP,' confirming webhook-based event subscription exists alongside the Gateway websocket API for events. However, the evidence pack gives only a single line on this capability with no detail on which events are supported, setup/config steps, or independent developer confirmation. Missing for 10: full list of subscribable event types, setup/configuration docs, and third-party/community validation of webhook event delivery in practice.
- [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
- [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
- [claimed-docs] “They do not require a bot user or authentication to use.”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
Zulipnone0/10Evidence 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…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnDiscordnone0/10No evidence Discord itself generates AI insights or suggestions from a user's data; evidence only covers bots/APIs, webhooks, threads, Nitro perks, and the Social SDK, none of which describe native AI-generated insights inside the product.
Zulipnone0/10No 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.
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnDiscord's developer platform provides Gateway (persistent WebSocket) and webhook APIs that let bots run continuously in the background reacting to events, and third parties can build bots that act autonomously (e.g., CI/CD notifications). However, this requires custom bot development rather than a built-in no-code 'automation' feature for end users, and there's no evidence of a first-party AI-native automation/workflow builder. Missing for 10: native no-code automation/workflow feature for non-developer users, AI-specific automation tooling, and independent evidence of autonomous background agents working reliably in practice.
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
- [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
- [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
- [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
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…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnDiscordnone0/10Discord's evidence covers building bots/apps via developer APIs, but there is no evidence of a built-in first-party AI assistant that users can delegate tasks to within the product itself.
ai-native userOperate the product with natural-language commands
weight 2 · round drawnDiscordnone0/10Discord's documented command system is built around structured slash commands, buttons, and modals (discord-docs-7/8/9/19/28/48), not natural-language interpretation of user requests; no evidence shows Discord itself parses free-form natural language to drive actions. The axis is plausible for a chat platform but nothing in the evidence demonstrates it.
- [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
- [claimed-docs] “Buttons are clickable components that can be customized with different styles, texts, and emoji.”
- [claimed-docs] “Modals are single-user pop-up interfaces that allow apps to collect form-like data.”
- [claimed-docs] “Application commands provide users a native way to invoke an app in Discord.”
- [claimed-docs] “Application commands provide users a native way to invoke an app in Discord. They often map to an app’s core features or functionality.”
- [claimed-docs] “Interactive features like commands and message components allows users to invoke an app natively within Discord.”
Zulipnone0/10Zulip'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…”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to ZulipDiscordnone0/10Discord's developer docs describe REST/Gateway/OAuth2 concepts and provide markdown-based reference pages, but the probe explicitly found no OpenAPI/Swagger spec (all candidate paths 404'd) and no evidence of an interactive, runnable-example API console or sandbox exists in the pack.
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways:”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.discord.com/openapi.json, https://docs.discord.com/swagger.json, https://docs.discord.c…”
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"}…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to ZulipDiscordnone0/10Discord provides REST API documentation and an llms.txt for docs indexing, but a direct probe for OpenAPI/swagger specs at all standard paths (openapi.json, swagger.json, api/openapi.json, .well-known/openapi.json) returned 404s, indicating no downloadable machine-readable API spec is published.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.discord.com/openapi.json, https://docs.discord.com/swagger.json, https://docs.discord.c…”
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
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, …”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnDiscordnone0/10The evidence pack covers Discord's API surfaces (REST, Gateway, OAuth2, webhooks, Social SDK) but contains no documentation or mention of API versioning scheme, version deprecation timelines, or a changelog/deprecation policy for developers to rely on. Missing for 10: explicit API version documentation (e.g., v9/v10), a published deprecation policy, and changelog/migration guides.
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
Zulipnone0/10While 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.
App platform — stories about app platform in this arenaApp platform
Stories about app platform in this arena
Apps
team-adminInstall prebuilt integrations from an app directory or marketplace
weight 3 · round to ZulipDiscord's docs confirm an App Directory — a searchable hub where users can browse apps/bots by name, category, or collection and add them to servers — which functions as a marketplace for prebuilt integrations (bots/apps). However, the evidence is entirely first-party docs about developer discovery/listing mechanics, with no detail on the admin-side installation/permission flow or independent confirmation of the experience. Missing for 10: independent/hands-on evidence of the admin installation UX, documentation of admin permission controls for installing apps, and confirmation beyond discovery-focused developer docs.
- [claimed-docs] “Once you've enabled discovery for your app, users can find it in the App Directory — a searchable hub where they can browse by name, categor…”
- [claimed-docs] “Once you’ve enabled discovery for your app, users can find it in the App Directory — a searchable hub where they can browse by name, categor…”
- [claimed-docs] “users can find it in the App Directory — a searchable hub where they can browse by name, category, or collection.”
- [claimed-docs] “users can find it in the App Directory — a searchable hub where they can browse by name”
- [claimed-docs] “Create shareable links to your app's profile page, store page, or specific items. Share these links in Discord, emails, or on your website.”
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”
developerRegister custom slash commands that users invoke from the message box
weight 2 · round to DiscordDiscord's docs clearly document slash commands ('application commands') as a native way for users to invoke apps by typing `/` in the chat box, with dedicated interactions/overview documentation covering registration and behavior. Missing for 10: independent hands-on developer corroboration and details on the actual registration API/code sample within this evidence pack.
- [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
- [claimed-docs] “Application commands provide users a native way to invoke an app in Discord.”
- [claimed-docs] “Application commands provide users a native way to invoke an app in Discord. They often map to an app’s core features or functionality.”
- [claimed-docs] “Interactive features like commands and message components allows users to invoke an app natively within Discord.”
Zulipnone0/10Zulip'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…”
developerBuild apps with rich interactive UI inside chat — modals, buttons, and structured message layouts
weight 2 · round to DiscordDiscord's developer docs explicitly document buttons, modals, slash/application commands, and message components as first-party interaction features for building rich in-chat UI (discord-docs-7,8,9,19,48). This directly matches the story's core ask. Missing for 10: no independent/hands-on developer corroboration of building a full interactive app, and no detail on select menus or full structured layout components beyond buttons/modals.
- [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
- [claimed-docs] “Buttons are clickable components that can be customized with different styles, texts, and emoji.”
- [claimed-docs] “Modals are single-user pop-up interfaces that allow apps to collect form-like data.”
- [claimed-docs] “Application commands provide users a native way to invoke an app in Discord.”
- [claimed-docs] “Interactive features like commands and message components allows users to invoke an app natively within Discord.”
- [claimed-docs] “Application commands provide users a native way to invoke an app in Discord. They often map to an app’s core features or functionality.”
Zulipnone0/10Evidence 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.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnDiscordnone0/10The evidence pack covers Discord's bot/API docs, OAuth2, webhooks, slash commands, and Social SDK, but nothing describes bulk endpoints or batch operations (e.g., bulk message delete, mass channel/role management) that an AI-native user could invoke to act on many items at once.
Zulipnone0/10While 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…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round drawnDiscord's Gateway API lets developer-built bots subscribe to server events and act on them, and webhooks let external systems post to Discord on events (e.g. CI/CD triggers), giving a technical path to event-driven automation. However, there is no evidence of a native, no-code 'if this then that' rule-builder for end users — all automation requires writing and hosting a bot/webhook integration. Missing for 10: a first-party no-code automation/rules UI, evidence of AI-native rule triggers, and independent confirmation that non-developer users can set this up.
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
- [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
- [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
- [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
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”
Bots integrations — stories about bots integrations in this arenaBots integrations
Stories about bots integrations in this arena
Ai agents
ai-native userAdd an AI agent as a member of a channel that participates in conversations when mentioned
weight 3 · round drawnDiscord's developer docs show a full bot platform — bot tokens, Gateway API for real-time message/event delivery, and application commands — that supports building an AI agent as a bot member of a server/channel, which is the standard mechanism for mention-triggered response bots. However, the evidence never explicitly documents mention-detection or an AI-agent-specific integration pattern, and there's no first-party or hands-on example of an AI agent responding when @mentioned in a channel. Missing for 10: explicit docs/example on mention-based triggering, hands-on/independent evidence of an AI agent bot working this way in production.
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “Application commands provide users a native way to invoke an app in Discord.”
- [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
- [claimed-docs] “Build bots and integrations on Discord, or connect your game with rich presence, voice chat, and more.”
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…”
ai-native userHave an agent read and post channel messages through the official API using scoped tokens
weight 3 · round to DiscordDiscord's official REST/Gateway API supports bot tokens and OAuth2 bearer tokens scoped to specific permissions, allowing an agent (bot) to read and post channel messages via documented endpoints and real-time Gateway events. missing for 10: no independent hands-on confirmation of an AI agent specifically using scoped tokens for message read/post, and no explicit documentation of granular message-read/post scopes beyond general bot/OAuth2 token mechanics.
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “Using a bot token found on the Bot page within your app’s settings... Using an OAuth2 bearer token gained through the OAuth2 API.”
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
- [claimed-docs] “OAuth2 enables application developers to build applications that utilize authentication and data from the Discord API.”
- [claimed-docs] “The first step in implementing OAuth2 is registering a developer application and retrieving your client ID and client secret.”
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…”
Bot api
developerPost a message into a channel with a simple incoming webhook URL
weight 2 · round to DiscordDiscord's docs explicitly describe incoming webhooks as a low-effort way to post messages to channels without requiring a bot user or authentication, and give concrete use cases like CI/CD pipelines posting notifications via HTTP. This directly matches the story of simple webhook-based posting. Missing for 10: independent hands-on developer confirmation of the webhook flow working in practice.
- [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
- [claimed-docs] “They do not require a bot user or authentication to use.”
- [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
- [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
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"}…”
developerBuild a bot that receives messages and events in real time through an events API or gateway connection
weight 3 · round to DiscordDiscord's documented Gateway API explicitly provides secure WebSocket connections for apps to receive real-time events (channel updates, role creation, etc.), and bot token authentication plus REST API access complete the developer bot-building path. Webhooks are also documented as an alternative for receiving/posting event notifications over HTTP. Missing for 10: independent hands-on developer confirmation of gateway reliability/rate limits and no direct community corroboration of real-time event handling in production.
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
- [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
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…”
Calls huddles — stories about calls huddles in this arenaCalls huddles
Stories about calls huddles in this arena
Ai notes
ai-native userGet AI-generated notes and recaps from meetings and huddles I attended or missed
weight 2 · round drawnDiscordnone0/10No evidence of any AI-generated meeting notes, transcription, or recap feature for Discord voice/huddle calls; the evidence pack covers bots, APIs, webhooks, Social SDK, and Nitro perks but nothing about AI summarization of calls. Missing for 10: any documentation or feature reference to AI-generated call transcripts, summaries, or recap generation.
Calls
team-adminStart an audio or video call directly from a channel or DM without leaving the app
weight 3 · round drawnDiscordnone0/10The evidence pack contains only developer/API documentation (bots, webhooks, OAuth2, Social SDK for games) and community commentary on unrelated topics like verification and moderation; none of it documents the core client feature of a user/admin starting a voice or video call directly from a text channel or DM inside the Discord app itself. Mentions of 'voice chat' (discord-docs-3, discord-docs-41) refer to the Social SDK for third-party games, not native in-app calling.
- [claimed-docs] “Add rich presence, voice chat, and social features to your game across all platforms.”
- [claimed-docs] “Build bots and integrations on Discord, or connect your game with rich presence, voice chat, and more.”
Channels threads — stories about channels threads in this arenaChannels threads
Stories about channels threads in this arena
External collaboration
team-adminCollaborate with external partners through guest accounts or shared channels with limited access
weight 2 · round to ZulipDiscordnone0/10The evidence pack shows Discord's developer platform, threads, and Nitro features but contains no mention of guest accounts, cross-org shared channels, or admin-controlled limited-access partner collaboration akin to Slack Connect. Threads (discord-docs-37, discord-docs-38) are an internal channel-branching feature, not external partner access control.
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.”
Messaging model
team-adminOrganize conversations into public and private channels with membership controls
weight 3 · round to ZulipEvidence confirms Discord supports organizing conversations into public and private sub-conversations (Threads, including 'Private Threads... rolling out to all servers') via discord-docs-37/38, which aligns with channel-like organization, but the pack contains no documentation of full channel-level permission/role systems, member/channel visibility controls, or admin management of channel membership that would fully substantiate the 'membership controls' part of the story. Missing for 10: explicit docs on channel permission overwrites/roles, admin UI for private channel membership, and any independent confirmation of these controls working as described.
- [claimed-docs] “A Thread is a quick way to branch a conversation off of a channel’s main feed without removing it from the channel itself.”
- [claimed-docs] “Private Threads are now available for all servers! This exciting update is rolling out to both desktop and mobile users now.”
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.”
team-adminReply in threads so side discussions stay attached to the original message
weight 3 · round to ZulipDiscord's blog docs confirm threads let users branch off a channel's main feed without removing context, including private threads for servers, which supports side-discussions staying attached to the original message. However, evidence doesn't explicitly confirm 'reply in thread' UX specifics or admin-specific thread controls. missing for 10: explicit documentation of admin thread permission controls, reply-to-message-in-thread UX detail, independent/hands-on corroboration beyond blog announcement.
- [claimed-docs] “A Thread is a quick way to branch a conversation off of a channel’s main feed without removing it from the channel itself.”
- [claimed-docs] “Private Threads are now available for all servers! This exciting update is rolling out to both desktop and mobile users now.”
- [claimed-docs] “Connect the Conversation with Threads on Discord”
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…”
team-adminCatch up on busy channels efficiently because every conversation is organized under a named topic or thread
weight 2 · round to ZulipDiscorddisputedcontradicted5/10Discord docs confirm threads let you branch conversations off a channel's main feed to organize topics (discord-docs-37, discord-docs-38, discord-docs-54), which is the core mechanism the story asks for. However, independent community reports describe channels/threads as chaotic when busy and poorly organized for catch-up, noting messages 'gate' content and become 'very chaotic when a lot of people are posting' and that Discord's UI/UX makes content hard to find intuitively (discord-comm-9, discord-comm-11). Missing for 10: evidence of thread-based read-state/summary tools for admins, and resolution of the chaos/discoverability complaints from real users.
- [claimed-docs] “A Thread is a quick way to branch a conversation off of a channel’s main feed without removing it from the channel itself.”
- [claimed-docs] “Private Threads are now available for all servers! This exciting update is rolling out to both desktop and mobile users now.”
- [claimed-docs] “Connect the Conversation with Threads on Discord”
- [community] “Discord, Slack, Gitter all gate messages so much, they are not well indexed by search engines and very chaotic when a lot of people are post…”
- [community] “I think Discord UI/UX is beyond terrible and Discord is nothing more than a terrible walled garden where none of the content has any discove…”
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…”
Notifications
team-adminTune notifications per channel, keyword, and schedule so only what matters interrupts me
weight 2 · round drawnDiscordnone0/10The evidence pack covers developer APIs, Nitro perks, Social SDK, threads, and community complaints, but contains no mention of Discord's actual notification settings features (per-channel mute/notification level, keyword/mention alerts, or scheduled quiet hours/Do Not Disturb) that a team-admin would use to tune interruptions.
Zulipnone0/10The 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.
Compliance exports — stories about compliance exports in this arenaCompliance exports
Stories about compliance exports in this arena
Compliance
platform-engineerReview audit logs of admin and user actions across the workspace
weight 2 · round drawnDiscordnone0/10No evidence of any audit-log feature for admin/user actions across a Discord server or workspace; the evidence pack covers developer APIs, bots, Nitro, Social SDK, and community sentiment, but nothing about compliance/audit logging capabilities for platform engineers.
platform-engineerEnforce message retention policies and legal holds for compliance and eDiscovery
weight 2 · round drawnDiscordnone0/10No evidence in the pack references message retention policies, legal holds, eDiscovery workflows, or compliance export tooling for platform engineers; the docs cover developer APIs, bots, Social SDK, and Nitro features only.
Zulipnone0/10The 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.
Exports
team-adminExport the full message history of my workspace in machine-readable formats, including private conversations where policy allows
weight 3 · round to ZulipDiscordnone0/10No evidence of any compliance-export tool, eDiscovery feature, or admin capability to export full message history (including private conversations) in machine-readable formats; the pack only covers developer APIs, bots, webhooks, Nitro, and Social SDK, none of which provide bulk/team-admin export of message history.
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.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to ZulipDiscord's developer platform exposes a broad REST/Gateway API, OAuth2, webhooks, slash commands, interactions, and a Social SDK covering messaging, presence, and account linking, showing substantial API coverage of bot/integration functionality. However, this coverage is aimed at building bots/apps rather than giving an end-user full parity with everything doable in the Discord client (e.g., no evidence of API-equivalent actions for Nitro subscription features, personal account social actions, or general UI-only settings), and the probe confirms no discoverable OpenAPI spec, suggesting the API surface isn't exhaustively documented for 1:1 parity. missing for 10: evidence of full end-user (non-bot) API parity for all client actions, an official OpenAPI/spec confirming complete surface coverage, and independent confirmation that no UI action lacks an API equivalent.
- [claimed-docs] “Build automated apps, commands, and integrations that run inside Discord servers.”
- [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
- [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
- [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
- [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.discord.com/openapi.json, https://docs.discord.com/swagger.json, https://docs.discord.c…”
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…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to ZulipDiscordnone0/10No evidence of a user-facing data export/portability feature or open-format data takeout for personal Discord data; the evidence pack covers developer APIs, bots, Nitro, and community complaints (e.g., loss of contact info on server bans, walled-garden criticism) rather than any account data-export capability. Missing for 10: documented data export/takeout tool, open-format (e.g., JSON) download of messages/DMs/servers, and any account deletion+portability workflow.
- [community] “One day I came to discover that Discord had banned the server for allegedly violating something. I wish I had written down everyone's emails…”
- [community] “I think Discord UI/UX is beyond terrible and Discord is nothing more than a terrible walled garden where none of the content has any discove…”
- [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
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'.”
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Pricing
team-adminKeep my team on a free tier without losing access to older message history
weight 2 · round drawnDiscordnone0/10No evidence in the pack addresses message history retention, archiving limits, or free-tier data access policies for Discord servers; the docs cover developer APIs, Nitro perks, and unrelated community topics.
Zulipnone0/10The 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.
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to ZulipDiscordnone0/10No evidence in the pack of Discord offering data residency/region selection controls for where user data is stored; documentation covers bots, APIs, SDKs, and Nitro features but nothing about data locality controls.
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”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnDiscordnone0/10No evidence of any AI-training data opt-out control, privacy setting, or policy statement addressing use of user data for AI/ML model training; evidence pack covers developer platform, bots, Nitro features, and unrelated community complaints (verification, moderation, breaches).
Zulipnone0/10No 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.
ai-native userControl data retention and deletion
weight 2 · round to ZulipDiscordnone0/10The evidence pack contains no documentation of data retention settings, data export, or account/message deletion controls for Discord users; it only shows unrelated developer API docs and community complaints about ID verification and a data breach, none of which describe actual retention/deletion controls.
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”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnDiscordnone0/10No evidence of any telemetry opt-out or privacy/data-tracking settings; the evidence pack covers developer APIs, Nitro features, and community complaints about verification/breaches, none of which address telemetry opt-out controls.
Search knowledge — stories about search knowledge in this arenaSearch knowledge
Stories about search knowledge in this arena
Ai catchup
ai-native userGet AI-generated summaries and recaps of channels and threads I missed
weight 2 · round drawnDiscordnone0/10No evidence of any native Discord feature that generates AI summaries or recaps of missed channels/threads; docs cover bots, OAuth2, webhooks, threads, Social SDK, and Nitro perks but nothing about AI-generated recap/summary functionality. A third-party bot could theoretically add this, but no such capability is evidenced for Discord itself.
- [claimed-docs] “A Thread is a quick way to branch a conversation off of a channel’s main feed without removing it from the channel itself.”
- [claimed-docs] “Private Threads are now available for all servers! This exciting update is rolling out to both desktop and mobile users now.”
- [claimed-docs] “Connect the Conversation with Threads on Discord”
Search
team-adminSearch the full message history with filters like sender, channel, and date
weight 3 · round to ZulipDiscordnone0/10The evidence pack contains no documentation or first-party reference to Discord's message search feature or its filters (sender, channel, date); all docs items focus on the developer API, bots, Nitro, and Social SDK. Community evidence even suggests messages are 'chaotic' and poorly indexed, but that speaks to external search engines, not an admin search UI, so it doesn't confirm the capability either.
- [community] “Discord, Slack, Gitter all gate messages so much, they are not well indexed by search engines and very chaotic when a lot of people are post…”
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…”
Workflow automation — stories about workflow automation in this arenaWorkflow automation
Stories about workflow automation in this arena
Workflow builder
team-adminBuild no-code workflows triggered by events, schedules, or form submissions inside the chat tool
weight 3 · round drawnDiscordnone0/10Discord's evidence pack shows only developer-oriented building blocks—webhooks, bot tokens, Gateway API events, slash commands—which require writing and hosting code, not a no-code workflow builder for triggers/schedules/forms. There is no mention of any built-in no-code automation canvas, scheduled triggers, or form-submission triggers akin to Slack Workflow Builder or Zapier.
- [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
- [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
- [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
- [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
- [claimed-docs] “Modals are single-user pop-up interfaces that allow apps to collect form-like data.”
Zulipnone0/10Zulip'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”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableDiscordn/aDiscord is a chat/social/gaming communication platform with bots, webhooks, and OAuth2 APIs for third-party integrations, not an AI agent or assistant product that would host/consume MCP servers as tools. The story's axis (plugging MCP servers into a product so it can use their tools) applies to AI-native agent/assistant products, not to a messaging platform's developer API surface.
Zulipn/aZulip is a team chat/communication platform, not an AI agent or assistant; there is no evidence of MCP client functionality allowing it to plug in and use MCP servers' tools. This is a category mismatch — MCP client integration applies to AI agents/assistants, not to a chat product like Zulip (though it does offer bots/integrations, those are unrelated to MCP).
ai-native userConnect an agent via an official MCP server
weight 3 · not comparableDiscordn/aDiscord is a chat/community platform, not an AI agent product, so connecting agents via an official MCP server is a category error for this evidence pack — no evidence of an MCP server exists, and the axis doesn't fit Discord's role as a communications platform rather than an agent tooling provider.
Zulipnone0/10Zulip 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…”
ai-native userUse an official CLI
weight 2 · not comparableDiscordn/aDiscord is a chat/community platform, not a CLI-oriented dev tool; the evidence covers APIs, bots, webhooks, and SDKs but no official CLI, and a CLI is not a fair expectation for this product category.
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…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableDiscordn/aDiscord is a communication/social platform, not a service offering a sandbox/staging environment for testing against production-equivalent data; this axis is a category error for this product type.
Zulipnone0/10The 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.
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableDiscordn/aDiscord is a communication/social platform, not a workflow/automation scheduling product; scheduling recurring jobs is outside its core product category, though third-party bots could theoretically add this, no evidence exists of Discord itself offering job scheduling.
Zulipnone0/10Zulip 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”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableDiscordn/aDiscord is a chat/community platform, not an automation-building tool with version control, review, or rollback features for workflows; this axis targets automation platforms (e.g., Zapier, GitHub Actions) rather than a communications product like Discord.
Zulipn/aZulip is a team chat platform, not an automation/workflow-building tool with a concept of 'automations' that could be versioned, reviewed, or rolled back; while it supports bots/integrations, there's no evidence of any automation-authoring feature with version control or rollback semantics. This axis is a category error for a chat product rather than an unmet capability.
team-adminShare my screen during a call for live collaboration
weight 2 · not comparableDiscordnone0/10The evidence pack contains extensive Discord developer/API docs and community commentary but no mention of native screen-sharing during voice/video calls, which is the core capability the story asks about. Absence of evidence for this mainstream Discord feature means it cannot be credited even though it likely exists in the product.
ai-native userRead the product's source under an open license
weight 2 · not comparableDiscordn/aDiscord is a closed-source, proprietary SaaS platform; source-code openness is not a plausible axis for this kind of product, and no evidence suggests any open-licensed source availability.
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'.”
ai-native userSelf-host the core product
weight 3 · not comparableDiscordn/aDiscord is a hosted proprietary SaaS chat platform with no self-hosted/open-source core offering; self-hosting is not a plausible axis for this product category, so this is a category error rather than a missing capability.
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.”