Slack vs Zulip for AI agents
As of 16 Oct 2026, Zulip gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Slack is a workplace chat app with a well-documented developer platform, but an agent can't sign up on its own: both the normal sign-up form and the free developer sandbox form show a 'prove you're not a robot' checkbox. To click it, the agent never got an account, so it couldn't send messages, make channels, or do anything else inside Slack.
Driven 16 Oct 2026 · The drive and its evidence- Find: Some docs for agents: An OpenAPI and an MCP server.
- Access: Sign-up in a browser.
- Use: 100% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
Through every checkpoint. Next: pay without a person
Gets in on its own and does nearly all the core work: L4 · Runs on its own. Signup needs a browser for an invisible ALTCHA proof-of-work, but it cleared on its own with no challenge shown; every other step, including getting a key and deactivating the organization, ran headless through the documented REST API. Through that API our agent created a channel, posted a message and read it back. No MCP, llms.txt or agent payment rail: paying runs through Stripe Checkout, asking for a card, cardholder name and billing address. Deletion works on its own: the API call set the account to deactivate, with data permanently removed after the server's standard waiting period.
Gets furtherDriven 6 Oct 2026 · The drive and its evidenceThe two summaries: written by our agents from each product's drive. How we write.
Where each one stops.
SlackStopped at sign up: needs a human
ZulipThrough every checkpoint
| Checkpoint | Slack | Zulip |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | In a browser |
| Verify | Not reached | Headless |
| Key | Not reached | Headless |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | In a browser |
| Cancel | Not reached | Not needed |
| Delete | Not reached | Headless |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Slack | Zulip | |
|---|---|---|
| Headless (checkpoints) | 1 | 6 |
| In a browser (checkpoints) | 0 | 2 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 100% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (third-party) |
| CLI | Yes | Yes |
| SDK | Yes | Yes |
| llms.txt | Yes | No |
Bot checks, and where a person was needed.
| Slack | Zulip | |
|---|---|---|
| Bot check | reCAPTCHA Enterprise (checkbox) stopped it at sign up, with a visible challenge | ALTCHA proof-of-work (first-party widget, /json/antispam_challenge) let it through at sign up |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | reCAPTCHA checkbox on the sign-up form | None |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Slack | Zulip | |
|---|---|---|
| Level | L1 · Needs a person | L4 · Runs on its own |
| Agent-ready setup | 100 of 100, good | 70 of 100, fair |
| Standards | OpenAPI 2.0 (3 versions behind) | OpenAPI 3.0.1 (2 versions behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Slack | Zulip | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | Headless |
How each one takes payment
- Slack: Payment not reached.
- Zulip: Reaches the checkout: stopped at the card form.
Slack vs Zulip: the short answers.
Which can an AI agent use, Slack or Zulip?
Zulip gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Slack our agent was stopped at sign up (needs a human); with Zulip it went through every checkpoint. Driven 16 Oct 2026 (Slack) and 6 Oct 2026 (Zulip).
Can an AI agent sign up for Slack and Zulip on its own?
Slack: no, needs a human. Zulip: yes, in a browser.
Do Slack and Zulip have an MCP server?
Slack: yes (official). Zulip: yes (third-party).
Can an AI agent delete its Slack or Zulip account?
Slack: not reached. Zulip: yes, headless.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.