Superhuman Mail vs Zero

Multi account

1. switcherConnect several accounts across providers — Gmail, Microsoft 365, IMAP — and work them from one place

   weight 3 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman clearly supports connecting and instantly switching between multiple Gmail and Outlook/Microsoft 365 accounts from one place (docs-12, docs-19, docs-20, docs-24, docs-40, docs-53), which covers two of the three providers in the story. However, no evidence mentions generic IMAP account support, so the 'switcher from any IMAP provider' part of the story is unaddressed. Missing for 10: explicit IMAP account support/connection, independent/hands-on confirmation of multi-provider account switching beyond vendor docs.

   • [claimed-docs] “you can instantly switch between Outlook and Gmail accounts without switching apps.”
   • [claimed-docs] “You can add all your Gmail and Outlook account calendars, and easily toggle them on and off.”
   • [claimed-docs] “you can instantly switch between Outlook and Gmail accounts without switching apps”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [claimed-docs] “it's available for [Gmail](https://blog.superhuman.com/gmail-alternatives/) and [Outlook](https://blog.superhuman.com/outlook-alternatives/)…”
   • [claimed-docs] “It helps you move faster, save time, respond sooner, and eliminate email anxiety. And it's available for Gmail and Outlook.”

   proof ↗⚑ flag

   Zero!disputedcontradicted4/10

   Zero's marketing repeatedly claims a 'Unified Inbox' connecting Gmail, Outlook, 'and more,' but the only hands-on/community description of the actual product (zero-comm-1) says it 'works on top of Gmail' and is in public beta, suggesting multi-provider (Microsoft 365, IMAP) support isn't yet realized in practice — no IMAP mention anywhere in the pack. Missing for 10: explicit IMAP support, confirmed working Microsoft 365/Outlook connection, and independent verification that multiple accounts can be worked from one place simultaneously.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Portability

1. switcherMy mail stays reachable over open protocols and standard formats — IMAP/JMAP/SMTP access and standards-based export — so no client can lock me in

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Superhuman is a proprietary client layered on top of Gmail/Outlook accounts; the evidence pack contains no mention of IMAP/JMAP/SMTP access, standards-based export, or any data-portability guarantee — only MCP integration for AI assistants and account switching between Gmail/Outlook. No documentation addresses protocol-level openness or export, so switchers have no evidence their mail stays reachable outside Superhuman's own app.

   ⚑ flag

   Zero—none0/10

   Evidence shows Zero connects to providers like Gmail/Outlook and offers self-hosting and an MCP server for AI actions, but nothing in the pack mentions IMAP/JMAP/SMTP protocol access or standards-based mail export for portability — the core of this switcher story is unaddressed.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [claimed-docs] “Self-hosting capabilities”

   proof ↗⚑ flag

2. switcherSelf-host the email app and keep the mail pipeline under my own control

   weight 1 · round to Zero
   Superhuman Mail—none0/10

   Superhuman Mail is a cloud SaaS client layered on top of Gmail/Outlook accounts; there is no evidence of any self-hosted deployment option, open-source server, or ability to run the mail pipeline on infrastructure the user controls. All evidence points to a hosted, proprietary service with no self-host path, so this axis is not delivered.

   ⚑ flag

   Zero✓fullprobed7/10

   Zero is explicitly open-source and self-hostable, with GitHub docs stating 'Self-Hosting Freedom – Run your own email app with ease' and a probe confirming a real, keyless-cloneable source tree with docker-compose files for self-hosting the full mail pipeline (DB, prod services). This gives a switcher genuine control over their own instance rather than relying on a hosted SaaS. Missing for 10: detailed self-hosting setup/migration docs (e.g. IMAP/SMTP backend specifics), independent hands-on reports of a completed self-hosted deployment, and confirmation of full mailbox portability beyond Gmail/Outlook OAuth integration.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Self-hosting capabilities”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Zero
   Superhuman Mail—none0/10

   The probe explicitly shows llms.txt returns 404 and no agent-oriented docs (openapi/well-known) are found; while an MCP server exists, there's no evidence of llms.txt or similar agent-discovery docs a user could point an agent at.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   The repo ships an AGENT.md (agent-configuration doc) and a detailed MCP.md describing the MCP server's tool surface, both of which are exactly the kind of machine/agent-oriented documentation an AI agent could be pointed at; this was confirmed by a hands-on probe of the actual repo tree. However there is no evidence of a dedicated llms.txt file or any explicit guidance framing these docs as an 'agent-readable spec' in the llms.txt convention. Missing for 10: an actual llms.txt file, first-party statement that docs are structured for LLM consumption, and independent confirmation an agent successfully parsed these docs.

   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Superhuman Mail is a GUI email client with an MCP server and agent triggers, but there is no evidence of a CLI, API, or documented mode to run the product headlessly or invoke it from a CI pipeline — probes for llms.txt and OpenAPI specs both returned 404. The story is plausible for an AI-native product with automation features, so it is not out of scope, but no evidence supports the specific headless/CI capability.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Superhuman Mail—none0/10

   All evidence describes Superhuman Mail acting as an MCP *server* that Claude/ChatGPT connect to (docs-10, docs-37, docs-24, probe-3), not Superhuman itself consuming external MCP servers' tools as a client. There is no evidence that a user can plug third-party MCP servers into Superhuman so it gains their tools.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   Zero—none0/10

   All evidence describes Zero exposing its own email/label/compose tools via an official 'ZeroMCP' server for other AI agents to consume — i.e., Zero acting as an MCP server/provider, not as a client that plugs in external MCP servers to use their tools. There is no documentation of Zero itself connecting to third-party MCP servers to extend its own toolset.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Superhuman Mail✓fullprobed8/10

   Superhuman documents an official Mail MCP server that connects Claude, ChatGPT, and other AI assistants to the inbox/calendar for summarizing, drafting, sending, and scheduling, with explicit send-approval controls, confirmed by a dedicated probe finding the official MCP page. Missing for 10: independent/hands-on third-party verification of the MCP server working (community evidence pack lacks any first-hand MCP usage reports) and technical details on the MCP server's implementation/spec compliance.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “Connect Claude or ChatGPT directly to your inbox to read, draft, and send emails with a single prompt — no copy-pasting required.”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a documented, named 'Zero MCP' server (MCP.md) exposing concrete tools (email CRUD, labels, AI compose, mailbox Q&A, web search) with an authentication method (Better Auth session token, OAuth coming soon), confirmed by an independent runtime probe finding the file in the actual repo. Missing for 10: independent hands-on verification that a third-party agent successfully connects and uses the server end-to-end, and OAuth is still unimplemented.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Superhuman Mail is an email client with an MCP integration and command palette (Cmd+K), but there is no evidence of an official CLI for AI-native workflows; probes for llms.txt/openapi also return 404, and no CLI is mentioned anywhere in docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [claimed-docs] “Cmd+K brings up Superhuman Command, where you can instantly do any action — and also learn the shortcut for next time.”
   • [claimed-docs] “In Superhuman, one shortcut rules them all: Cmd+K. Cmd+K brings up Superhuman Command, where you can instantly do any action”

   proof ↗⚑ flag

   Zero—none0/10

   Zero's evidence shows an MCP server (ZeroMCP) and self-hosting via docker-compose, plus a pnpm-based dev script for Drizzle Studio, but no official CLI tool for AI-native interaction with the product itself is documented anywhere in the pack.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “View and edit data with Drizzle Studio pnpm db:studio”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”

   proof ↗⚑ flag

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

   weight 3 · round to Zero
   Superhuman Mail~partialprobed6/10

   Superhuman ships a documented, public MCP server (email-mcp) that lets AI-native users drive inbox/calendar actions—summarize, draft, send, schedule—directly from Claude, ChatGPT and other AI tools, which is a real programmatic surface for agentic use. However, probes confirm there is no traditional REST/OpenAPI-documented public API (llms.txt and openapi.json endpoints all 404), so developers outside the MCP/AI-assistant flow have no documented way to integrate. Missing for 10: a general-purpose REST/GraphQL API with OpenAPI spec, and any independent/hands-on verification of the MCP server's reliability.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person. You can review the drafts in Superhuman Mail, or edit and …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a documented MCP server (ZeroMCP) exposing a public, structured API for emails, labels, AI compose, mailbox Q&A, and web search, with authentication documented via Better Auth session tokens (OAuth coming soon), corroborated by a runtime probe confirming the real MCP.md and AGENT.md files in the repo. missing for 10: independent third-party usage/testing of the MCP API beyond first-party docs and a single runtime probe, and full OAuth support (currently listed as coming soon).

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Evidence shows Superhuman Mail connects to Claude/ChatGPT via MCP and includes approval gates ('every send action requires explicit approval') plus admin-level 'connector permissions' governance, but there is no evidence of an actual scoped/least-privilege API credential or key system that an ai-native user can issue to individual agents. Probes for llms.txt and OpenAPI specs both return 404, suggesting no public API surface for credential scoping exists.

   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”

   proof ↗⚑ flag

   Zero—none0/10

   Zero's MCP server documents authentication via a Better Auth session token (or future OAuth), but there is no evidence of scoped or least-privilege credential issuance, permission granularity, or agent-specific token scoping — auth appears to be a single session-level token granting full account access. Missing for 10: any documentation of scopes/permissions models, per-agent credential minting, or restricted-access tokens for agents.

   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Zero
   Superhuman Mail—none0/10

   Evidence shows Superhuman ships an MCP server for AI assistants (docs-10, docs-37, probe-3) but there is no mention of official SDKs, client libraries, or public API documentation for developers; explicit probes for llms.txt and OpenAPI/Swagger specs both returned 404 (superhuman-probe-1, superhuman-probe-2), indicating no official SDK exists.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”

   proof ↗⚑ flag

   Zero~partialprobed5/10

   Zero doesn't publish a traditional language SDK, but it does document an official 'ZeroMCP' server (MCP.md) with concrete tool endpoints (email CRUD, labels, AI compose, mailbox Q&A) plus AGENT.md agent-configuration docs, giving AI-native developers a documented, official programmatic interface to build against, corroborated by a runtime probe confirming these files exist in the live repo. Missing for 10: an actual client SDK/library (Python/JS package), auth beyond a session token (OAuth marked 'coming soon'), and independent third-party developer usage reports.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [github] “🚀 Developer-Friendly – Built with extensibility and integrations in mind.”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Evidence shows Superhuman offers an MCP server for AI assistant integration and an agents/automation feature, but nothing describes webhook subscriptions or event-driven push notifications for external systems; API/OpenAPI probes also returned 404s, indicating no documented webhook API.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence covers Zero's MCP server (tool-calling actions like search, compose, label management) but nowhere mentions webhooks, event subscriptions, or push notifications for external systems to react to inbox events.

   ⚑ flag

Agentic features

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed9/10

   Superhuman Mail delivers extensive AI-generated insights from user data: Ask AI answers questions by mining inbox content (e.g., flight/hotel/offsite queries), Auto Drafts pull context from inbox, calendar, and web to write ready-to-send replies, Auto Labels classify and surface important emails, and read-status/follow-up nudges surface actionable insights. First-party docs are extensive and consistent across many features (Ask AI, Auto Drafts 2.0, Auto Labels, Email Assistant), though independent hands-on validation specifically of the AI-insight features (vs. general product commentary) is thin. Missing for 10: independent/hands-on corroboration specifically validating the accuracy or usefulness of AI-generated insights (most evidence is vendor-authored).

   • [claimed-docs] “You can now get rapid answers without having to remember senders, guess keywords, or comb through messages.”
   • [claimed-docs] “Just ask: _"where is the q2 offsite"_, _"when is my flight"_, _"where am I staying"_, and we'll immediately generate succinct answers.”
   • [claimed-docs] “Just ask: "where is the q2 offsite", "when is my flight", "where am I staying", and we'll immediately generate succinct answers.”
   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Each draft can use your inbox, calendar, and the web to write replies that are ready to send.”
   • [claimed-docs] “Every message that needs a reply comes with a draft written in your voice. Each draft can use your inbox, calendar, and the web to write rep…”
   • [claimed-docs] “Superhuman AI will automatically separate marketing, cold pitches, and social network updates, so you can respond faster to what matters mos…”
   • [claimed-docs] “With Auto Labels, Superhuman Mail automatically classifies incoming messages — so you can focus on what matters most.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”

   proof ↗⚑ flag

   Zero✓fullprobed7/10

   Zero documents AI features that generate insights from mailbox data: composing emails with AI assistance, answering questions about mailbox content and specific threads, and summarizing/chatting with inbox content, corroborated by founder description of AI-powered summarization and chat-with-inbox in community coverage. missing for 10: independent hands-on verification of insight quality/accuracy and no broader third-party review confirming these AI features work reliably in practice.

   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman documents proactive automations: Auto Archive/Auto Labels/Auto Drafts run automatically in the background, and a newer 'agents' feature lets users build proactive agents via chat or visual builder with admin-governed triggers and connectors. However, sending still requires explicit human approval, limiting true autonomy, and there is no independent/hands-on corroboration of the agent-builder feature working as described. Missing for 10: third-party verification of the visual builder/agent triggers, detail on failure/error handling for autonomous runs, and evidence of unattended send/execute actions.

   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [claimed-docs] “Superhuman AI can automatically archive marketing, cold pitches, and social network updates. Turn on Auto Archive, and eliminate inbox clutt…”
   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows an MCP server exposing on-demand email tools (search, compose, label, delete) that an AI client can call interactively, but nothing shows Zero itself scheduling or running autonomous background automations/triggers/workflows without a user or agent actively invoking them.

   ⚑ flag

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

   weight 3 · round drawn
   Superhuman Mail✓fullclaimed8/10

   Superhuman ships a built-in AI assistant that auto-labels, archives, drafts replies, answers questions, and now supports building proactive agents from triggers/connectors with admin governance, all documented extensively as first-party features (docs-2,6,25,27,38,61,62,64). This directly matches delegating tasks to an in-product AI assistant beyond simple automation. Missing for 10: independent/hands-on user reports specifically validating the delegation/agent-building experience (community evidence covers general product sentiment, not this AI-assistant delegation feature).

   • [claimed-docs] “Every email that needs a reply comes with a draft—you can just edit and send.”
   • [claimed-docs] “If your email needs a response, you’re automatically reminded to follow up—with a draft already written and ready to send.”
   • [claimed-docs] “Handle every follow-up with one prompt. Superhuman Mail can check which emails have been read, draft all the nudges, and send when each reci…”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”
   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person. You can review the drafts in Superhuman Mail, or edit and …”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero ships a built-in AI assistant that can compose emails, answer questions about threads/mailbox, and perform web search (Perplexity), confirmed both in docs (MCP.md) and independent community description of it as an 'AI-powered email client' that summarizes, drafts, and lets users chat with their inbox. Missing for 10: broader independent hands-on verification beyond a single HN comment, and clearer distinction between MCP-exposed tools vs. in-app assistant UX.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail✓fullprobed8/10

   Superhuman supports natural-language operation via Ask AI queries, plain-language personalization instructions, AI-prompt-based Auto Labels, and full MCP integration letting users drive inbox/calendar actions (summarize, draft, send, schedule) via Claude/ChatGPT with a single prompt. missing for 10: independent/hands-on verification of natural-language command accuracy and no first-party demo of complex multi-step NL commands beyond simple prompts.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “Connect Claude or ChatGPT directly to your inbox to read, draft, and send emails with a single prompt — no copy-pasting required.”
   • [claimed-docs] “Just ask: _"where is the q2 offsite"_, _"when is my flight"_, _"where am I staying"_, and we'll immediately generate succinct answers.”
   • [claimed-docs] “Add plain-language instructions like "write in lowercase" or "use this booking link" to personalize your writing and scheduling features.”
   • [claimed-docs] “You can even make your own Auto Labels with short AI prompts like "job applications" or "requests to review work".”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   Zero✓fullcommunity7/10

   Zero's founder describes it as an AI-powered email client where users can chat with their inbox, ask questions about threads, and have AI draft replies, and the MCP docs confirm natural-language driven actions (compose, search, ask questions, web search) — this directly matches AI-native NL command operation. Missing for 10: independent hands-on verification of the actual chat UI/NL command interface beyond founder claims and MCP protocol docs.

   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [claimed-docs] “Compose emails with AI assistance”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes explicitly confirm no OpenAPI/swagger spec and no llms.txt is available, and the MCP server page offers no interactive docs/playground.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is an email client with an MCP server and docs (MCP.md, ROADMAP.md), but there is no evidence of an interactive API reference (e.g., Swagger/OpenAPI explorer, Postman collection, or runnable code sandbox) for AI-native users to explore and execute example calls.

   ⚑ flag

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   Direct probes for OpenAPI/Swagger specs and llms.txt all returned 404s, and no documentation mentions a downloadable machine-readable API spec; only an MCP server is offered, which is a separate mechanism, not an API spec.

   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

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

   weight 1 · round drawn
   Superhuman Mail—none0/10

   No evidence anywhere in the pack mentions a sandbox, test/staging environment, or any way to develop or validate AI workflows against non-production data — the docs only describe production-facing features (MCP, auto-drafts, auto-labels) with no mention of test environments. missing for 10: any sandbox/staging environment, test data isolation, or dev-mode API/MCP endpoint separate from live inbox data.

   ⚑ flag

   Zero—none0/10

   Zero is an AI email client whose evidence covers MCP tools for real mailbox operations (send/delete/label emails) and self-hosting, but nothing describes a sandbox, test/staging mode, or mock data environment isolated from production email accounts.

   ⚑ flag

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

   weight 2 · round drawn
   Superhuman Mail—none0/10

   No evidence of any versioned public API or documented deprecation policy; probes for OpenAPI specs returned 404s, and there's no mention of API versioning or deprecation practices anywhere in the docs. The only developer-facing surface found is the MCP server, which is unrelated to API versioning guarantees. missing for 10: any public API documentation, version numbers, changelog/deprecation policy, or evidence of stable programmatic interfaces.

   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence describes Zero's MCP server capabilities and self-hosting, but no documentation anywhere mentions API versioning, version numbers, or a deprecation policy for its MCP/API surface. missing for 10: any mention of API versioning scheme, changelog/deprecation policy, or backward-compatibility guarantees.

   ⚑ flag

Agent workflows

1. ai-native userAn external agent — Claude, ChatGPT, or my own — can read, triage, draft, and send my email end to end through a documented connection

   weight 2 · round drawn
   Superhuman Mail✓fullprobed8/10

   Superhuman documents a first-party MCP server connecting Claude/ChatGPT (and other assistants) to inbox and calendar, enabling reading, summarizing, drafting, and sending emails via prompts, with explicit send-approval controls and an official MCP feature probe confirming the endpoint exists. missing for 10: independent/hands-on third-party verification of the MCP integration working end-to-end, and detail on triage/labeling actions being fully agent-driven rather than app-side AI.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “Connect Claude or ChatGPT directly to your inbox to read, draft, and send emails with a single prompt — no copy-pasting required.”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person. You can review the drafts in Superhuman Mail, or edit and …”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   Zero✓fullprobed8/10

   Zero documents an official MCP server (MCP.md, verified by probe) enabling agents like Claude to read threads, ask questions about mailbox content, compose with AI assistance, and create/send drafts and new emails, plus manage labels — covering triage, drafting, and sending end to end via Better Auth session token auth. missing for 10: no hands-on third-party report of an external agent (Claude/ChatGPT) actually completing a full read-triage-send workflow, and OAuth support is still 'coming soon' rather than shipped.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [claimed-docs] “You can connecto ZeroMCP using two methods: 1. Better Auth session token 2. OAuth (Coming soon)”
   • [probe] “official MCP server documented at https://github.com/Mail-0/Zero/blob/staging/MCP.md”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Ai assistant

1. ai-native userAsk an assistant questions across my whole inbox and calendar — who said what, what's outstanding — and get grounded answers

   weight 2 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed8/10

   Superhuman's Ask AI feature directly supports natural-language Q&A grounded in the inbox and calendar (e.g., 'where is the q2 offsite', 'when is my flight', 'where am I staying'), and the MCP integration extends this to Claude/ChatGPT for cross-inbox/calendar queries, drafting, and scheduling grounded in real data. Missing for 10: independent/hands-on evidence validating accuracy of 'grounded answers' across a full inbox+calendar corpus, and detail on how well it surfaces 'what's outstanding' beyond follow-up reminders.

   • [claimed-docs] “You can now get rapid answers without having to remember senders, guess keywords, or comb through messages.”
   • [claimed-docs] “Just ask: _"where is the q2 offsite"_, _"when is my flight"_, _"where am I staying"_, and we'll immediately generate succinct answers.”
   • [claimed-docs] “Just ask: "where is the q2 offsite", "when is my flight", "where am I staying", and we'll immediately generate succinct answers.”
   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Zero's MCP server explicitly supports asking questions about mailbox content and specific email threads, plus AI compose, search, and labels, and community commentary confirms an AI-powered 'chat with your inbox' experience. However, evidence doesn't show cross-inbox/whole-calendar synthesis, calendar integration, or 'who said what / what's outstanding' style grounded multi-thread reasoning — the documented Q&A appears scoped to mailbox/thread level rather than full inbox+calendar grounding. missing for 10: calendar integration/awareness, evidence of synthesizing across the entire inbox (not just single threads), independent hands-on verification of grounded multi-source answers.

   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Ai drafting

1. ai-native userAI drafts replies in my own voice and tone — ready to review and send, not generic boilerplate

   weight 3 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed9/10

   Superhuman's Auto Drafts feature explicitly writes replies in the user's own voice/tone (matching style from sent emails, even per-recipient), pulling context from inbox/calendar/web, and presents them ready to edit and send rather than generic boilerplate — with explicit human approval before sending. This is well-documented across first-party docs with consistent detail; missing for 10: independent/hands-on user corroboration of draft quality/voice-matching accuracy beyond vendor claims.

   • [claimed-docs] “Just jot down some phrases, and we'll turn them into a full email. Best of all, the email sounds like you. Superhuman AI matches the voice a…”
   • [claimed-docs] “Every message that needs a reply comes with a draft written in your voice.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person.”
   • [claimed-docs] “Every draft matches your voice and tone, using your unique style for each person. You can review the drafts in Superhuman Mail, or edit and …”
   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Each draft can use your inbox, calendar, and the web to write replies that are ready to send.”
   • [claimed-docs] “Every message that needs a reply comes with a draft written in your voice. Each draft can use your inbox, calendar, and the web to write rep…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “with Auto Drafts 2.0, every message that needs a reply comes with a draft. You can just edit and send.”

   proof ↗⚑ flag

   Zero~partialcommunity5/10

   Zero's MCP docs and founder description confirm AI drafts replies ('Compose emails with AI assistance', 'drafts replies') as a core feature, but no evidence describes voice/tone personalization or learning the user's writing style. Missing for 10: documentation of voice/tone matching or personalization mechanism, and independent hands-on verification that drafts read as the user's own voice rather than generic AI text.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Ai triage

1. ai-native userAI triages my inbox for me — auto-labeling, categorizing, and surfacing what needs attention — with behavior I can steer and audit

   weight 3 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed8/10

   Superhuman documents auto-labeling ('Auto Labels'), custom AI-prompt categories, auto-archiving of low-priority mail, inbox splitting into topic tabs, and immediate labeling on arrival — directly matching triage/categorization needs. Steerability is evidenced via custom prompt-based Auto Labels, plain-language instructions, and admin governance controls, plus auditability via draft review before sending and explicit send approval. missing for 10: independent/hands-on validation of triage accuracy or audit trail is absent, and community evidence is largely about UI/performance rather than AI triage quality.

   • [claimed-docs] “Superhuman AI can automatically archive marketing, cold pitches, and social network updates. Turn on Auto Archive, and eliminate inbox clutt…”
   • [claimed-docs] “Superhuman AI will automatically separate marketing, cold pitches, and social network updates, so you can respond faster to what matters mos…”
   • [claimed-docs] “You can even make your own Auto Labels with short AI prompts like "job applications" or "requests to review work".”
   • [claimed-docs] “Turn on Auto Archive, and eliminate inbox clutter for good.”
   • [claimed-docs] “Auto Labels, Superhuman AI will automatically separate marketing, cold pitches, and social network updates, so you can respond faster to wha…”
   • [claimed-docs] “you can make your own Auto Labels with short AI prompts, and then split your inbox into tabs using these custom Auto Labels.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”
   • [claimed-docs] “Emails are labeled the moment they arrive, so you can see what's important and what's not.”
   • [claimed-docs] “Custom Auto Labels let you categorize emails with your own AI prompts. (Available for our Business and Enterprise customers.)”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Community and docs evidence show Zero markets itself as an AI-powered inbox that auto-categorizes emails, and its MCP server exposes tools to modify/create labels, filter/search by label, and answer questions about threads/mailbox content, giving a steerable interface for AI actions. However, there's no explicit documentation of automatic prioritization/surfacing of 'what needs attention' or an audit log of AI triage decisions beyond the generic MCP action list. Missing for 10: dedicated 'needs attention' surfacing/prioritization feature, explicit audit trail or history of AI-taken triage actions, and independent hands-on verification of auto-labeling accuracy.

   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”
   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Create new custom labels with custom colors”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

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

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman supports batch-style operations like Auto Archive, Auto Labels, and 'Handle every follow-up with one prompt' (checking read status, drafting all nudges, sending in bulk) plus MCP-driven workflows that run across the whole inbox/calendar, giving genuine bulk automation for triage, labeling, and follow-ups. However, this is scoped to email/calendar items only and there's no evidence of arbitrary bulk operations across many items in a single explicit action (e.g., bulk delete/move/tag N selected emails via UI or API in one command) or bulk operation limits/performance at scale. missing for 10: evidence of explicit multi-item bulk actions (e.g., select-and-bulk-process UI), scale/performance data on bulk automation, and independent/hands-on confirmation of bulk operations working reliably.

   • [claimed-docs] “Handle every follow-up with one prompt. Superhuman Mail can check which emails have been read, draft all the nudges, and send when each reci…”
   • [claimed-docs] “Superhuman Mail can check which emails have been read, draft all the nudges, and send when each recipient is most likely to open it.”
   • [claimed-docs] “Turn on Auto Archive, and eliminate inbox clutter for good.”
   • [claimed-docs] “Superhuman AI can automatically archive marketing, cold pitches, and social network updates. Turn on Auto Archive, and eliminate inbox clutt…”
   • [claimed-docs] “You can even make your own Auto Labels with short AI prompts like "job applications" or "requests to review work".”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”

   proof ↗⚑ flag

   Zero~partialprobed5/10

   Zero's MCP server exposes email actions like 'Bulk delete emails' and 'Bulk archive emails' explicitly labeled as bulk operations, plus label/search operations that could apply across many items. However, evidence does not specify limits, batch size, or confirm bulk semantics beyond these two named actions, nor is there hands-on confirmation of bulk behavior at scale. missing for 10: independent/hands-on verification of bulk operations at scale, documentation of batch limits or performance, evidence of bulk operations beyond delete/archive (e.g., bulk label/move/send).

   • [claimed-docs] “Bulk delete emails - Bulk archive emails”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

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

   weight 3 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed7/10

   Superhuman documents explicit rule/trigger-based automation: custom Auto Labels driven by user-defined AI prompts, Auto Archive, Auto Drafts, and a stated capability to "create agents that run proactively based on triggers you set and the work you connect" with admin governance over agent building. This directly matches the ai-native automation-depth story of defining rules that fire actions on events. missing for 10: independent/hands-on verification of the rule engine's reliability and richer documentation of trigger/condition/action logic beyond marketing copy.

   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [claimed-docs] “You can even make your own Auto Labels with short AI prompts like "job applications" or "requests to review work".”
   • [claimed-docs] “you can make your own Auto Labels with short AI prompts, and then split your inbox into tabs using these custom Auto Labels.”
   • [claimed-docs] “Custom Auto Labels let you categorize emails with your own AI prompts. (Available for our Business and Enterprise customers.)”
   • [claimed-docs] “Superhuman AI can automatically archive marketing, cold pitches, and social network updates. Turn on Auto Archive, and eliminate inbox clutt…”
   • [claimed-docs] “Turn on Auto Archive, and eliminate inbox clutter for good.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero as an AI email client with MCP tool actions (search, compose, label, etc.) but no documented rule-based automation engine that triggers actions on events (e.g., 'when email arrives from X, do Y'). All actions appear to be user- or agent-invoked rather than event-triggered automation. Missing for full credit: any documented trigger/condition/action rules engine or scheduled/event-based automation feature.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed5/10

   Superhuman documents 'agents that run proactively based on triggers you set' and MCP-driven 'workflows that run across your inbox and calendar,' suggesting some automation/triggering capability, but there's no detail on recurring/scheduled job mechanics (e.g., cron-like scheduling, workflow persistence) and no independent/hands-on corroboration. Missing for 10: explicit recurring-schedule configuration details, independent verification that these agent workflows actually run repeatedly/reliably, and more than a passing marketing mention.

   • [claimed-docs] “Use chat or our visual builder to create agents that run proactively based on triggers you set and the work you connect.”
   • [claimed-docs] “Admins govern who can build agents and control connector permissions across the entire org from one place.”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is an AI email client with MCP tools for email actions (labels, search, compose, AI Q&A) but no evidence of scheduling recurring jobs or workflows/automation triggers.

   ⚑ flag

Calendar

1. power-userSee my calendar, respond to invites, and create events without leaving the email client

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman Calendar lets users view their day in the email side panel, add/toggle multiple calendars, and use 'Find Time' to schedule meetings with teammates across time zones, all without leaving the client. However, none of the evidence explicitly confirms responding to/RSVPing on calendar invites or manually creating new calendar events from within the client. Missing for 10: explicit invite-response (accept/decline) capability, explicit event-creation UI/flow evidence, independent hands-on confirmation of calendar features.

   • [claimed-docs] “Simply add teammates, click "Find Time", and instantly see when everyone is free.”
   • [claimed-docs] “You can add all your Gmail and Outlook account calendars, and easily toggle them on and off.”
   • [claimed-docs] “When any email mentions a date, Superhuman Mail will show your day in the right side panel — so you always have context.”
   • [claimed-docs] “Working across time zones? Add a secondary time zone, so scheduling between San Francisco and New York (or London and Tokyo) is effortless.”
   • [claimed-docs] “Add a secondary time zone, so scheduling between San Francisco and New York (or London and Tokyo) is effortless.”

   proof ↗⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2. power-userShare my availability or insert bookable meeting times directly into an email

   weight 1 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed7/10

   Superhuman's Auto Drafts explicitly 'insert availability' pulled from your calendar (docs-38), the Calendar feature lets you 'Find Time' to instantly see when teammates are free (docs-7), and users can add plain-language instructions like 'use this booking link' to personalize scheduling in drafts (docs-9, docs-54, docs-60). Missing for 10: independent/hands-on verification of this exact workflow and more detail on native booking-link generation vs. relying on a user-supplied link.

   • [claimed-docs] “Auto Drafts now gather context from your inbox, your calendar, and the web. They can use information from other emails, insert availability,…”
   • [claimed-docs] “Simply add teammates, click "Find Time", and instantly see when everyone is free.”
   • [claimed-docs] “Add plain-language instructions like "write in lowercase" or "use this booking link" to personalize your writing and scheduling features.”
   • [claimed-docs] “Add plain-language instructions like "write in lowercase" or "use this booking link" to personalize your writing and schedul”
   • [claimed-docs] “Add plain-language instructions like "write in lowercase" or "use this booking link" to personalize your writing”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is an email client with AI/MCP features for composing, searching, and managing emails, but no evidence in the pack mentions calendar integration, availability sharing, or inserting bookable meeting times into emails.

   ⚑ flag

Sending

1. power-userSee whether and when recipients opened my email

   weight 1 · round to Superhuman Mail
   Superhuman Mail~partialcommunity6/10

   Superhuman docs confirm read-status tracking ('check which emails have been read', 'Read statuses are now shared across your team') and community evidence (superhuman-comm-1, criticizing image-based tracking as 'spying') independently corroborates that read/open tracking is a real, functioning feature. However, no evidence explicitly confirms a timestamped 'when opened' view for individual recipients—only binary read/unread status and team-level sharing are documented. Missing for 10: explicit per-recipient open-time timestamps, hands-on verification of accuracy/reliability of the read-tracking mechanism.

   • [claimed-docs] “Handle every follow-up with one prompt. Superhuman Mail can check which emails have been read, draft all the nudges, and send when each reci…”
   • [claimed-docs] “Superhuman Mail can check which emails have been read, draft all the nudges, and send when each recipient is most likely to open it.”
   • [claimed-docs] “Team Read Statuses: Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [community] “"Superhuman doesn't even let its own customers turn images off. So merely by using Superhuman, you are vulnerable to the exact same spying t…”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions read receipts, open tracking, or notifications about when recipients open emails; the MCP/docs only cover sending, drafting, labeling, and searching emails.

   ⚑ flag

2. power-userSchedule an email to send later and undo a send within a grace window

   weight 2 · round drawn
   Superhuman Mail—none0/10

   No evidence in the pack mentions scheduled send or an undo-send grace window feature for Superhuman Mail; the docs cover AI drafting, labeling, MCP integration, and other features but nothing about delayed/scheduled sending or send-undo functionality.

   ⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions scheduled send or undo-send functionality; MCP docs list send/draft/delete but nothing about delayed sending or a grace-window recall.

   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts”

   proof ↗⚑ flag

Templates

1. power-userInsert saved snippets or templates — with variables and attachments — instead of retyping the same reply

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed5/10

   Superhuman's Snippets feature is well documented — insert commonly-used phrases, paragraphs, or whole emails via keyboard shortcut, and share snippets across a team — directly matching the 'saved templates instead of retyping' part of the story. However, no evidence mentions variable/placeholder support (e.g., auto-filled name/date fields) or attaching files as part of a snippet/template. Missing for 10: variable/placeholder support in snippets, attachment bundling within snippets, independent hands-on confirmation of these specifics.

   • [claimed-docs] “Insert commonly-used phrases, paragraphs, or whole emails with a simple keyboard shortcut.”
   • [claimed-docs] “You can also share Snippets with your team, so your team can move faster, with consistent, up-to-date, and high-performing messaging.”
   • [claimed-docs] “Snippets can now be shared across your team, so you can all work faster with current and consistent messaging.”
   • [claimed-docs] “With Snippets, you can automate typing and push past this limit. Insert commonly-used phrases, paragraphs, or whole emails with a simple key…”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence pack item mentions saved snippets, canned responses, or templates with variables/attachments; the docs describe AI-assisted composing, MCP tools, labels, and self-hosting but nothing about a snippet/template insertion feature.

   ⚑ flag

Offline

1. power-userRead, search, and write email offline, with changes syncing when I reconnect

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed5/10

   Superhuman's own docs repeatedly claim the app 'works perfectly offline' and even when the connection is terrible, suggesting core reading/composing functionality persists without a network. However, there is no explicit documentation of offline search behavior or how changes (sent drafts, read/archive actions) reconcile once reconnected, and no independent/hands-on corroboration of offline sync reliability. missing for 10: explicit description of offline search indexing, detail on conflict resolution/sync-on-reconnect mechanics, and third-party verification of offline behavior.

   • [claimed-docs] “Superhuman gives you a new way to work with Gmail. It works perfectly offline.”
   • [claimed-docs] “Superhuman gives you a new way to work with Gmail. It works perfectly offline. It works even when online, and your internet connection is te…”
   • [claimed-docs] “It works perfectly offline. It works even when online, and your internet connection is terrible.”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions offline mode, local caching, or sync-on-reconnect; Zero appears to be a web-based email client requiring live connection to providers/AI services, with no offline-capability documentation.

   ⚑ flag

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

   weight 2 · round to Zero
   Superhuman Mail~partialprobed5/10

   Superhuman exposes an official MCP server (email-mcp) letting AI assistants read, draft, send emails, summarize threads, and schedule meetings — a real but curated subset of UI actions — while probes show no public REST/OpenAPI spec (404s on openapi.json/llms.txt), meaning many UI capabilities (Auto Labels config, split inbox, Snippets, team features, Command palette, offline mode) have no documented API equivalent. Missing for 10: full OpenAPI/REST documentation, evidence of parity for non-email/calendar UI features (labels, snippets, team collaboration, command palette), and independent confirmation that MCP covers 1:1 UI functionality.

   • [claimed-docs] “Superhuman Mail MCP connects your inbox and calendar into Claude, ChatGPT, and other AI assistants—so you can summarize threads, draft and s…”
   • [claimed-docs] “Connect Claude or ChatGPT directly to your inbox to read, draft, and send emails with a single prompt — no copy-pasting required.”
   • [claimed-docs] “Connect all your Gmail and Outlook accounts, including work, personal, and side projects. Manage every inbox and calendar from one AI assist…”
   • [claimed-docs] “You can now drive Superhuman Mail from Claude, ChatGPT, and your favorite AI tools. You can create powerful workflows that run across your i…”
   • [claimed-docs] “Every send action requires your explicit approval, so you stay in control.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://superhuman.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://superhuman.com/openapi.json, https://superhuman.com/swagger.json, https://superhuman.com/api…”
   • [probe] “official MCP server documented at https://superhuman.com/mail/features/email-mcp”

   proof ↗⚑ flag

   Zero~partialprobed6/10

   Zero's MCP server exposes many core email actions (search, send, draft, delete, labels, AI compose, thread Q&A) that mirror UI functionality, giving strong API-parity for mail operations. However missing for 10: no evidence of API parity for UI-specific settings like customizable keyboard shortcuts, UI theming/customization, unified inbox provider management, or account/connection setup via API — these remain UI-only per docs, and there's no independent confirmation the MCP surface is fully comprehensive versus a curated subset.

   • [claimed-docs] “Compose emails with AI assistance”
   • [claimed-docs] “Ask questions about specific email threads”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Ask questions about mailbox content - Ask questions about specific email threads”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”
   • [claimed-docs] “Customizable keyboard shortcuts”
   • [github] “Customizable UI & Features – Tailor your email experience the way you want it.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Superhuman Mail—none0/10

   No evidence of any data export capability, open-format export, or account portability/exit tooling in the evidence pack; the product is an email client layered on Gmail/Outlook but nothing documents exporting Superhuman-specific data (labels, snippets, agent configs) or facilitating leaving the platform. missing for 10: data export feature docs, open format (e.g. mbox/CSV/JSON) support, migration/exit tooling, any independent confirmation of portability.

   ⚑ flag

   Zero—none0/10

   Evidence shows Zero is self-hostable, open-source, and doesn't sell user data, plus a Drizzle Studio DB viewer for self-hosters, but there is no documented data-export feature (e.g., mbox/EML export, takeout tool) letting a user extract all their mail data in an open format and leave the service.

   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [claimed-docs] “View and edit data with Drizzle Studio pnpm db:studio”

   proof ↗⚑ flag

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

   weight 2 · round to Zero
   Superhuman Mail—none0/10

   Superhuman Mail is closed-source proprietary SaaS; no evidence of any open-licensed source availability. missing for 10: any mention of open-source license, public repository, or source availability.

   ⚑ flag

   Zero✓fullprobed8/10

   Zero's source is publicly hosted on GitHub (Mail-0/Zero) with a full contributing guide, self-hosting instructions, and a verified runtime probe confirming a real, clonable source tree with Docker configs for self-hosting — consistent with an open-source project freely readable by AI-native users. Missing for 10: explicit citation of the license file/name (e.g. MIT/AGPL) to confirm licensing terms.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “View and edit data with Drizzle Studio pnpm db:studio”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Zero
   Superhuman Mail—none0/10

   Superhuman Mail is a proprietary SaaS email client; no evidence anywhere in the pack indicates a self-hostable version, on-prem deployment, or open-source core. All evidence describes a cloud-hosted product with API/MCP integrations, not self-hosting options.

   ⚑ flag

   Zero✓fullprobed8/10

   Multiple GitHub and docs citations explicitly advertise 'Self-Hosting Freedom' and describe running your own email app, and a runtime probe confirms a real self-hostable source tree with docker-compose files for self-hosting deployment. Missing for 10: independent hands-on report of a completed self-host deployment beyond the repo/docker-compose evidence, and more detailed self-host setup documentation.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “⚙️ **Self-Hosting Freedom** – Run your own email app with ease.”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “Self-hosting capabilities”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

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

   weight 2 · round to Zero
   Superhuman Mail—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or storage location choices for Superhuman Mail; the axis applies to an email/data platform but no capability is documented.

   ⚑ flag

   Zero~partialclaimed5/10

   Zero's self-hosting capability (own infra, own database via docker-compose) lets a user effectively choose where their data lives, and it claims not to track/collect/sell data, but there is no explicit region/residency selection feature or documented multi-region hosted offering. missing for 10: explicit region/residency selection UI or hosted multi-region options, documentation on data locality guarantees for the hosted SaaS version, independent confirmation of self-host deployment satisfying residency requirements.

   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “⚙️ **Self-Hosting Freedom** – Run your own email app with ease.”
   • [claimed-docs] “Self-hosting capabilities”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [github] “Zero does not track, collect, or sell your data in any way.”

   proof ↗⚑ flag

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

   weight 3 · round to Zero
   Superhuman Mail—none0/10

   No evidence in the pack addresses data usage for AI model training, opt-out settings, or any privacy/data-retention policy statement — the evidence pack is entirely about feature functionality (AI drafting, labeling, MCP, calendar) with no mention of training-data controls. missing for 10: any privacy policy statement on AI training data usage, an opt-out or opt-in toggle for model training, or third-party confirmation of data handling practices.

   ⚑ flag

   Zero~partialclaimed5/10

   Zero states it does not track, collect, or sell user data, and self-hosting is available which would let users fully control data flow, implying no AI training on user data. However, there is no explicit statement or policy about AI-model training exclusion (e.g., no clause addressing whether email content sent to AI features like compose/summarize is used for model training). missing for 10: explicit AI-training opt-out/data-use policy, third-party AI provider data-handling terms, independent verification of the no-training claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Zero
   Superhuman Mail—none0/10

   The evidence pack contains no mention of data retention settings, deletion controls, or data lifecycle policies for Superhuman Mail or its AI/MCP features—only feature descriptions, community sentiment, and unrelated probes. This is a fair privacy-posture question for an AI-native email product, but no evidence shows such controls exist.

   ⚑ flag

   Zero~partialclaimed5/10

   Zero claims a no-tracking/no-sell data policy and supports self-hosting (giving users full control over their own data and deletion since they own the infrastructure), plus MCP tools include explicit 'delete emails' actions. However, there's no documented data retention policy, no explicit account/data deletion workflow or export tooling described, and no independent verification of the no-tracking claim. missing for 10: documented retention/export/deletion policy for hosted use, independent audit of data practices, explicit account-deletion or right-to-be-forgotten flow.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “gives users the power to **self-host** their own email app”
   • [github] “gives users the power to self-host their own email app while also integrating external services like Gmail and other email providers”
   • [claimed-docs] “Get email threads by ID - List emails in specific folders - Create and send new emails - Create email drafts - Send existing drafts - Delete…”
   • [claimed-docs] “Bulk delete emails - Bulk archive emails”

   proof ↗⚑ flag

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

   weight 2 · round to Zero
   Superhuman Mail—none0/10

   No evidence pack item addresses telemetry, analytics opt-out, or usage-tracking controls; one community comment even notes Superhuman does not let users disable image-loading tracking, but this doesn't constitute a documented telemetry opt-out and can't establish 'disputed' since no vendor claim of an opt-out exists to contradict.

   ⚑ flag

   Zero~partialprobed5/10

   Zero's GitHub page states it 'does not track, collect, or sell your data in any way,' and self-hosting support (Docker compose files, self-hosting docs) lets AI-native users run their own instance with no vendor telemetry at all. However there is no explicit telemetry settings/opt-out toggle documented, no privacy policy detail, and no independent verification of the no-tracking claim. Missing for 10: explicit telemetry opt-out control/setting, detailed privacy policy, and independent/hands-on confirmation of the no-tracking claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”
   • [github] “Self-Hosting Freedom – Run your own email app with ease.”
   • [github] “⚙️ Self-Hosting Freedom – Run your own email app with ease.”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless shallow git clone of Mail-0/Zero landed a REAL self-hostable source tree — repo-root MCP.md (…”

   proof ↗⚑ flag

Protection

1. switcherUse aliases or masked addresses so sign-ups and strangers never learn my real address

   weight 1 · round drawn
   Superhuman Mail—none0/10

   No evidence anywhere in the pack mentions email aliasing, masked/anonymous addresses, or any feature to hide a user's real address from sign-ups or strangers; Superhuman's documented features focus on AI triage, drafting, scheduling, and MCP integrations, not address privacy. Missing for 10: any mention of alias generation, masked email addresses, or privacy-relay/forwarding features.

   ⚑ flag

   Zero—none0/10

   Zero is an AI-powered unified email client with labels, search, and MCP integrations, but nothing in the evidence pack describes email alias generation or masked/burner address creation to hide a user's real address from sign-ups or strangers.

   ⚑ flag

2. switcherThe client protects me from senders' tracking — blocking read pixels by default — and is transparent about what it does with my mail data

   weight 2 · round to Zero
   Superhuman Mail—none0/10

   No documentation claims Superhuman blocks tracking pixels by default or explains transparent data handling; in fact, community evidence explicitly states Superhuman does not let users disable images/tracking pixels, meaning senders' read-tracking is not blocked. No privacy-policy or data-handling transparency evidence is present either.

   • [community] “"Superhuman doesn't even let its own customers turn images off. So merely by using Superhuman, you are vulnerable to the exact same spying t…”

   proof ↗⚑ flag

   Zero~partialclaimed3/10

   Only a general privacy claim ('Zero does not track, collect, or sell your data in any way') is evidenced, with no mention of read-pixel/tracking-pixel blocking specifically or a detailed data-handling policy. missing for 10: explicit read-receipt/tracking-pixel blocking feature, documentation of default-on behavior, a privacy policy detailing mail data handling, and independent confirmation of the no-tracking claim.

   • [github] “Zero does not track, collect, or sell your data in any way.”

   proof ↗⚑ flag

Migration

1. switcherImport my complete mail history and contacts from my old provider or client

   weight 1 · round drawn
   Superhuman Mail—none0/10

   No evidence in the pack describes importing mail history or contacts from another provider/client; Superhuman only connects live Gmail/Outlook accounts, with no mention of migration, historical import, or contact import tools. Missing for 10: any documentation of import/migration functionality, historical mail transfer, or contact import from other providers.

   ⚑ flag

   Zero—none0/10

   Zero connects to providers like Gmail/Outlook for unified inbox access, but no evidence describes any import/migration tool for bulk historical mail or contacts from an old provider/client — no mention of mbox/EML import, contact list import, or migration wizard.

   ⚑ flag

Search

1. power-userSearch is fast and precise — operators, filters, and ranked results across my full mail history

   weight 2 · round to Zero
   Superhuman Mail!disputedcontradicted4/10

   Superhuman markets 'Ask AI' as a way to get answers without keyword search (docs-4, docs-18, docs-26) but the evidence pack contains no documentation of actual search operators, filters, or ranked-results syntax across full mail history. A hands-on ex-user reports search was actually slow ('ten seconds' vs Gmail's instant) contradicting the 'fastest email' marketing, while another user reports search is 'blazing fast' (superhuman-comm-7 vs superhuman-comm-9), creating a genuine dispute rather than settled capability. missing for 10: documented search operator syntax, filter capabilities, ranked-results mechanism, and independent confirmation resolving the speed contradiction.

   • [claimed-docs] “You can now get rapid answers without having to remember senders, guess keywords, or comb through messages.”
   • [claimed-docs] “Just ask: _"where is the q2 offsite"_, _"when is my flight"_, _"where am I staying"_, and we'll immediately generate succinct answers.”
   • [claimed-docs] “Just ask: "where is the q2 offsite", "when is my flight", "where am I staying", and we'll immediately generate succinct answers.”
   • [community] “"I am an ex-user. A search through my email archive would regularly take ten seconds while gmail would do it instantly... my experience was …”
   • [community] “"My experience is that search and UI transitions are blazing fast. It crashes (rarely, but more than I like) and requires a restart. But I l…”

   proof ↗⚑ flag

   Zero~partialcommunity4/10

   Evidence shows a basic 'search emails with custom queries' and 'filter by labels' capability via the MCP server, but there is no documentation of advanced operators, ranked relevance, or performance/scale across full mail history; a community comment even flags missing basic navigation features, suggesting search UX is still immature. missing for 10: documented search operators/syntax, evidence of ranking/relevance across full historical mail, performance benchmarks, independent hands-on confirmation of search speed/precision.

   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”
   • [claimed-docs] “Compose emails with AI assistance - Ask questions about mailbox content - Ask questions about specific email threads - Web search using Perp…”

   proof ↗⚑ flag

Shortcuts

1. power-userDo everything from the keyboard — comprehensive shortcuts and a command palette — in an interface fast enough to never make me wait

   weight 3 · round to Superhuman Mail
   Superhuman Mail!disputedcontradicted6/10

   Superhuman documents a comprehensive Cmd+K command palette that surfaces every action and teaches shortcuts (docs-8, docs-34) plus fast reply shortcuts (docs-67), fitting the keyboard-power-user story. However, hands-on community reports are split: some users call it 'blazingly fast' (comm-9), while at least one ex-user reports search taking ten seconds vs instant in Gmail, directly contradicting the 'never wait' claim (comm-7), and another calls the UI just a 'cuter UI' around Gmail features with no real speed edge (comm-12). Missing for 10: a documented exhaustive keyboard-shortcut reference beyond the command palette, and independent benchmark data resolving the conflicting speed reports.

   • [claimed-docs] “Cmd+K brings up Superhuman Command, where you can instantly do any action — and also learn the shortcut for next time.”
   • [claimed-docs] “In Superhuman, one shortcut rules them all: Cmd+K. Cmd+K brings up Superhuman Command, where you can instantly do any action”
   • [claimed-docs] “You can reply to important messages faster with blazingly fast shortcuts and features like Instant Intro.”
   • [community] “"I am an ex-user. A search through my email archive would regularly take ten seconds while gmail would do it instantly... my experience was …”
   • [community] “"My experience is that search and UI transitions are blazing fast. It crashes (rarely, but more than I like) and requires a restart. But I l…”
   • [community] “"They essentially just teach you how to do things that gmail already lets you do, but put a cuter UI around it, and they force teach you con…”

   proof ↗⚑ flag

   Zero!disputedcontradicted2/10

   Zero's own roadmap lists 'customizable keyboard shortcuts' as a planned (not yet shipped) feature, and a hands-on community comment explicitly states the product lacks 'real keyboard navigation' today, directly contradicting any power-user keyboard-first claim; no command palette is mentioned anywhere in the evidence. missing for 10: shipped keyboard shortcut system, command palette, any evidence of interface speed/responsiveness for power users.

   • [claimed-docs] “Customizable keyboard shortcuts”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”

   proof ↗⚑ flag

Channels

1. team-leadThe same inbox also handles adjacent customer channels — SMS, WhatsApp, social, or live chat — beside email

   weight 1 · round drawn
   Superhuman Mail—none0/10

   All evidence is about email (Gmail/Outlook) plus calendar integration; there is no mention of SMS, WhatsApp, social, or live chat channels being unified into the same inbox. The product is positioned strictly as an email/calendar client with AI and MCP integrations, not an omnichannel customer messaging platform.

   ⚑ flag

   Zero—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Routing

1. team-leadAssign conversations to teammates and route incoming mail with rules so ownership is explicit

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed4/10

   Superhuman offers team-collaboration signals like shared read statuses, reply indicators, and @mention team comments that help avoid duplicate work, plus shared snippets and team scheduling — but there is no evidence of formal conversation assignment or rule-based mail routing that establishes explicit ownership of a thread to a specific teammate. Missing for 10: dedicated 'assign to teammate' functionality, configurable routing/ownership rules for incoming mail, and any independent confirmation these team features work as advertised.

   • [claimed-docs] “Team Read Statuses: Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “Team Reply Indicators: See when your team is replying, so you can avoid double work and embarrassing collisions.”
   • [claimed-docs] “let you @mention teammates, share live email views, and coordinate responses without external recipients seeing internal discussions”
   • [claimed-docs] “Snippets can now be shared across your team, so you can all work faster with current and consistent messaging.”
   • [claimed-docs] “Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “See when your team is replying, so you can avoid double work and embarrassing collisions.”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is a personal AI-powered email client with unified inbox, labels, and MCP tooling, but no evidence anywhere in the pack describes team features like assigning conversations to teammates or configuring routing/ownership rules — capabilities relevant for shared team inboxes. This is a fair axis for an email client, but no evidence supports it, so it's 'none' rather than 'na'.

   ⚑ flag

Shared inbox

1. team-leadWe can discuss an email in an internal side-thread — comments and @mentions beside the message — instead of forwarding copies around

   weight 2 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed8/10

   Superhuman's Team Comments feature explicitly supports @mentioning teammates, sharing live email views, and coordinating internal discussion without external recipients seeing it — directly matching the story's side-thread/comment use case, backed by Team Read Statuses and Reply Indicators for coordination. Missing for 10: independent/hands-on validation of the comment threading UX and details on comment persistence/notification workflow beyond vendor blog claims.

   • [claimed-docs] “let you @mention teammates, share live email views, and coordinate responses without external recipients seeing internal discussions”
   • [claimed-docs] “Team Read Statuses: Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “Team Reply Indicators: See when your team is replying, so you can avoid double work and embarrassing collisions.”
   • [claimed-docs] “Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “See when your team is replying, so you can avoid double work and embarrassing collisions.”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence covers email management, MCP AI features, and self-hosting, but nothing describes internal side-threads with comments/@mentions for team discussion of emails without forwarding.

   ⚑ flag

2. team-leadMy team works shared inboxes together — shared accounts or team channels where everyone sees the same conversation state

   weight 3 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman ships several team-collaboration features that approximate shared inbox awareness — team read statuses, reply indicators to avoid double-replies, team comments for internal coordination without external visibility, and shared snippets/scheduling — giving a team-lead's group real-time visibility into who's handling what (superhuman-docs-49,50,51,55,56,71,72,73). However, this is built on individually-owned mailboxes with cross-visibility signals, not a true shared/group inbox or shared account model where the whole team works one conversation queue with assignment/ownership. Missing for 10: evidence of a genuine shared mailbox/account model, ticket-style assignment of conversations, and independent confirmation of how well these team signals work in practice.

   • [claimed-docs] “Team Read Statuses: Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “Team Reply Indicators: See when your team is replying, so you can avoid double work and embarrassing collisions.”
   • [claimed-docs] “Team Scheduling: See when your team is free, so you can schedule at the speed of thought.”
   • [claimed-docs] “let you @mention teammates, share live email views, and coordinate responses without external recipients seeing internal discussions”
   • [claimed-docs] “Snippets can now be shared across your team, so you can all work faster with current and consistent messaging.”
   • [claimed-docs] “Read statuses are now shared across your team, so anybody can follow up with full context.”
   • [claimed-docs] “See when your team is replying, so you can avoid double work and embarrassing collisions.”
   • [claimed-docs] “See when your team is free, so you can schedule at the speed of thought.”

   proof ↗⚑ flag

   Zero—none0/10

   Zero is positioned as a personal AI-powered unified inbox for individual users (Gmail/Outlook accounts), with no evidence of shared inboxes, team channels, or shared conversation state across multiple users; features described are individual email management, MCP tooling, and self-hosting, not multi-user collaboration.

   • [github] “Unified Inbox – Connect multiple email providers like Gmail, Outlook, and more.”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag

Followups

1. power-userSnooze conversations and set follow-up reminders that resurface a thread if nobody replies

   weight 2 · round to Superhuman Mail
   Superhuman Mail~partialclaimed6/10

   Superhuman documents an automated follow-up reminder system that drafts nudges and resurfaces threads needing a response when no reply has come ('automatically reminded to follow up—with a draft already written', 'check which emails have been read, draft all the nudges, and send when each recipient is most likely to open it'), closely matching the reminder half of the story. However, there is no explicit mention of a 'snooze' feature to temporarily hide a conversation and resurface it later, which is a core part of the story. Missing for 10: explicit snooze/defer-conversation functionality, independent/hands-on confirmation of the follow-up reminder behavior.

   • [claimed-docs] “If your email needs a response, you’re automatically reminded to follow up—with a draft already written and ready to send.”
   • [claimed-docs] “If your email needs a response, you're automatically reminded to follow up—with a draft already written and ready to send.”
   • [claimed-docs] “Handle every follow-up with one prompt. Superhuman Mail can check which emails have been read, draft all the nudges, and send when each reci…”
   • [claimed-docs] “Superhuman Mail can check which emails have been read, draft all the nudges, and send when each recipient is most likely to open it.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”
   • [claimed-docs] “works inside Gmail and Outlook to label, declutter, draft, and remind automatically”

   proof ↗⚑ flag

   Zero—none0/10

   No evidence anywhere in the pack mentions snooze, follow-up reminders, or resurfacing threads after no reply; the documented features cover labels, search, compose, AI Q&A, and self-hosting only.

   ⚑ flag

Inbox structure

1. power-userSelect many conversations at once and archive, label, or mark them done in one stroke

   weight 1 · round to Zero
   Superhuman Mail~partialclaimed3/10

   Superhuman documents AI-driven Auto Archive and Auto Labels that batch-classify/archive whole categories of mail automatically, plus a command palette (Cmd+K) said to 'instantly do any action,' and split-inbox tabs to 'get through emails of the same type, at the same time' — all of which gesture at bulk triage outcomes, but none explicitly describe a manual multi-select-then-archive/label/mark-done workflow across many conversations. Missing for 10: explicit documentation or independent confirmation of manual multi-select bulk actions (checkbox/shift-click select many threads, then batch archive/label/mark-done in one keystroke).

   • [claimed-docs] “Turn on Auto Archive, and eliminate inbox clutter for good.”
   • [claimed-docs] “you can focus on a specific topic — and get through emails of the same type, at the same time.”
   • [claimed-docs] “Get an email assistant that automatically labels incoming emails, archives low-priority messages, drafts replies, and reminds you to follow …”
   • [claimed-docs] “In Superhuman, one shortcut rules them all: Cmd+K. Cmd+K brings up Superhuman Command, where you can instantly do any action”
   • [claimed-docs] “splitting your inbox allows you to divide your inbox into different areas of focus — based on the types of email you receive mos”

   proof ↗⚑ flag

   Zero~partialcommunity4/10

   Zero's MCP docs explicitly list 'Bulk delete emails' and 'Bulk archive emails' plus label modification tools, showing some bulk-action capability, but this is exposed via an AI/MCP tool interface rather than confirmed as a native UI multi-select action, and there's no mention of a 'mark done' state or how many items can be selected/acted on interactively. Community commentary even flags gaps in basic power-user UI ergonomics (no real keyboard navigation), suggesting bulk in-UI triage may be immature. missing for 10: confirmed UI multi-select archive/label/done action, evidence of a 'done' state, independent hands-on confirmation of bulk UI workflow.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Bulk delete emails - Bulk archive emails”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [community] “hoping to see some more discussion here - i'd love to replace superhuman. However, until Zero has real keyboard navigation, i'll have to wai…”

   proof ↗⚑ flag

2. power-userSplit my inbox into focused streams — important, team, newsletters, calendar invites — so triage happens in priority order, not arrival order

   weight 3 · round to Superhuman Mail
   Superhuman Mail✓fullclaimed8/10

   Superhuman explicitly documents 'split inbox' functionality with custom categories like VIP, Notifications, Calendar, and Team, plus custom Auto Labels that let users organize incoming mail into tabs by type so triage happens by focus area rather than arrival order. This is a first-party documented feature with a dedicated blog post, not just a vague claim. missing for 10: independent/hands-on confirmation of the split-inbox feature specifically (community evidence covers other aspects of Superhuman but not this feature) and detail on how priority ordering interacts with arrival order within each stream.

   • [claimed-docs] “in Superhuman Mail, you can design your own categories: like "VIP", "Notifications", "Calendar", or "Team".”
   • [claimed-docs] “you can design your own categories: like "VIP", "Notifications", "Calendar", or "Team".”
   • [claimed-docs] “splitting your inbox allows you to divide your inbox into different areas of focus — based on the types of email you receive mos”
   • [claimed-docs] “splitting your inbox allows you to divide your inbox into different areas of focus — based on the types of email you receive most”
   • [claimed-docs] “you can make your own Auto Labels with short AI prompts, and then split your inbox into tabs using these custom Auto Labels.”
   • [claimed-docs] “you can make your own Auto Labels with short AI prompts, and then split your inbox into tabs using these custom Auto Labels”
   • [claimed-docs] “you can focus on a specific topic — and get through emails of the same type, at the same time.”
   • [claimed-docs] “Custom Auto Labels let you categorize emails with your own AI prompts. (Available for our Business and Enterprise customers.)”

   proof ↗⚑ flag

   Zero—none0/10

   Evidence shows Zero supports labels, filtering, unified inbox, and AI Q&A, but there is no mention of dedicated inbox streams/views separating important, team, newsletter, and calendar-invite emails for priority-ordered triage. Labeling/filtering capabilities exist but no evidence of a stream-based triage UI or auto-categorized views as described in the story.

   • [claimed-docs] “Modify email labels”
   • [claimed-docs] “Search emails with custom queries - Filter emails by labels”
   • [claimed-docs] “Get all user labels - Create new custom labels with custom colors - Delete existing labels”
   • [community] “Zero founder describes it as an AI-powered email client that auto-categorizes, summarizes threads, drafts replies, and lets users chat with …”

   proof ↗⚑ flag