Email Clients & Email AI Arena
Shortwave vs AgentMail
AgentMail wins · 12–14 (9 drawn)
Accounts openness — stories about accounts openness in this arenaAccounts openness
Stories about accounts openness in this arena
Portability
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 to AgentMailShortwavenone0/10Shortwave's own founder states they integrate via Gmail's proprietary APIs 'not IMAP,' and there is no mention anywhere in docs of JMAP, SMTP-level access, or standards-based export tooling — the product only works atop Google's servers (also confirmed by a security-focused user noting 'it only works with Google servers'). No evidence of any open-protocol mail access or portable export path exists in the pack.
- [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”
- [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
AgentMail documents IMAP/SMTP compatibility, letting any standard mail client (Outlook, Thunderbird, Apple Mail) connect to an AgentMail inbox, which supports the open-protocol reachability part of the story. However, there is no mention of JMAP support or of a standards-based export/data-portability mechanism for migrating mail elsewhere. Missing for 10: JMAP protocol support, documented mailbox/data export or migration tooling, and independent confirmation that IMAP/SMTP access works reliably in practice.
- [claimed-docs] “Connect Outlook, Thunderbird, Apple Mail, or any IMAP/SMTP-compatible client to your AgentMail inbox”
switcherSelf-host the email app and keep the mail pipeline under my own control
weight 1 · round drawnShortwavenone0/10Shortwave is a cloud-hosted email client that syncs data to its own servers and works only with Gmail/Google servers (per community reports), with no documentation of any self-hosting option, on-prem deployment, or open-source pipeline; probes for docs/API specs also return 404s, indicating no infrastructure exposed for self-hosting.
- [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
- [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
- [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
- [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
AgentMailnone0/10AgentMail is documented as a hosted email API/service (custom domains, hosted MCP server, webhooks) with no mention anywhere of a self-hosted deployment option; a competitor's marketing even highlights itself as the 'self-hosted drop-in replacement' for AgentMail, implying AgentMail itself is cloud-only.
- [claimed-docs] “using your own custom domains is essential for production applications. It gives you control over your sending reputation, which is the sing…”
- [claimed-docs] “AgentMail runs a hosted MCP server at https://mcp.agentmail.to/mcp that exposes inbox, message, thread, draft, and attachment tools to any c…”
- [community] “agentmail charges $20/mo for 10 inboxes. autopilot gives you unlimited inboxes for the cost of a postgres row, positioning itself as a self-…”
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to AgentMailShortwavenone0/10Direct probes show no llms.txt or agent-oriented docs endpoint exists (404s across llms.txt, docs-md, openapi paths), and no other evidence mentions such agent-facing documentation.
AgentMail hosts a live llms.txt file (verified HTTP 200) with a clear agent-oriented summary of its docs, and its entire documentation set is written in agent-consumable .md format (e.g., quickstart.md, messages.md) alongside an OpenAPI spec, MCP server, and CLI docs, making it easy for an agent to be pointed at and consume its docs. Missing for 10: no independent/community confirmation of an agent successfully navigating llms.txt end-to-end.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.agentmail.to/llms.txt # AgentMail | Documentation > AgentMail is an email API built for AI agents.…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.agentmail.to/openapi.json — contains "openapi" key”
- [claimed-docs] “The agent registers itself using the human email you provide and gets back an API key, inbox ID, and organization ID.”
- [probe] “official MCP server documented at https://docs.agentmail.to/integrations/mcp”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to AgentMailShortwavenone0/10The 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.)
AgentMail is fundamentally API/SDK-driven ('Create, manage, and operate email inboxes entirely via API'), with a documented OpenAPI spec, official CLI, and webhook/websocket event delivery that support scripted, non-interactive automation pipelines. No explicit CI/CD example or pipeline walkthrough is given, so full CI-specific validation is inferred rather than directly documented. Missing for 10: an explicit CI/CD pipeline example or GitHub Actions integration, and independent confirmation of headless use in production automation.
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
- [claimed-docs] “Create inboxes, send messages, manage threads, and more — all without writing code.”
- [claimed-docs] “Instead of constantly asking the AgentMail API if there's a new email (a process called polling), you can register a URL, and we will send y…”
- [claimed-docs] “you can register a URL, and we will send you a `POST` request with the details as soon as an event happens.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.agentmail.to/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://docs.agentmail.to/integrations/cli”
ai-native userConnect an agent via an official MCP server
weight 3 · round to AgentMailShortwavenone0/10Shortwave documents letting its own AI Assistant connect out to third-party MCP servers ('Add custom integration', point to an MCP server of your choice) — this is MCP-client behavior, not Shortwave exposing an official MCP server that external agents could connect to. As a SaaS email product, offering an official MCP server for outside agents is a fair, applicable axis, but no evidence pack item shows such a server (docs/openapi/llms.txt probes all 404).
- [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
- [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
- [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
- [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
AgentMail is a service/API product (not itself an agent), so the MCP-server axis applies, and docs confirm a hosted official MCP server at https://mcp.agentmail.to/mcp exposing inbox, message, thread, draft, and attachment tools to any compatible client, corroborated by a probe hit. Missing for 10: independent/hands-on confirmation that the MCP server works reliably in practice beyond first-party docs.
- [claimed-docs] “AgentMail runs a hosted MCP server at https://mcp.agentmail.to/mcp that exposes inbox, message, thread, draft, and attachment tools to any c…”
- [claimed-docs] “AgentMail runs a hosted MCP server at `https://mcp.agentmail.to/mcp` that exposes inbox, message, thread, draft, and attachment tools to any…”
- [probe] “official MCP server documented at https://docs.agentmail.to/integrations/mcp”
ai-native userDrive the product through a documented public API
weight 3 · round to AgentMailShortwavenone0/10Shortwave's evidence only shows it acting as an MCP *client* (connecting its AI Assistant to other apps' MCP servers) or integrating with third-party APIs like Zapier/GitHub — none of this constitutes Shortwave itself exposing a documented public API for external developers to drive the product. Direct probes for llms.txt, docs-as-markdown, and OpenAPI/Swagger specs all returned 404s, confirming no discoverable public API surface.
- [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
- [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
- [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
- [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
AgentMail is explicitly an API-first product: docs describe registering agents via API, creating inboxes, sending/searching messages, webhooks, permissions, etc., and a live OpenAPI spec is confirmed at docs.agentmail.to/openapi.json. This gives strong first-party and probe-verified evidence of a documented, comprehensive public API. Missing for 10: independent third-party hands-on validation of the API itself (community feedback focuses on website/pricing, not API usage).
- [claimed-docs] “The agent registers itself using the human email you provide and gets back an API key, inbox ID, and organization ID.”
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.agentmail.to/openapi.json — contains "openapi" key”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.agentmail.to/llms.txt # AgentMail | Documentation > AgentMail is an email API built for AI agents.…”
- [claimed-docs] “Instead of constantly asking the AgentMail API if there's a new email (a process called polling), you can register a URL, and we will send y…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to AgentMailShortwavenone0/10Shortwave's evidence covers MCP/app integrations and AI assistant features, but there is no mention of scoped or least-privilege API credential issuance, API key management, or granular permission controls for agents; probes confirm no public API/OpenAPI spec exists. Community comments even note complaints about over-broad permission requests rather than scoped credentials, reinforcing absence of this capability.
- [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
- [community] “User complaint: 'all these apps either want gmail way too many gmail permissions, and/or are hosted... I'm trying to get rid of gmail lol.'”
Docs explicitly describe scoped API keys restricted to a single pod or inbox, per-customer pods with scoped keys for multi-tenancy, and a dedicated Permissions feature to restrict what an API key can do — directly matching the least-privilege credential story. Missing for 10: independent/hands-on verification that scoping actually enforces restrictions in practice, and detail on granularity of permission types beyond pod/inbox scope.
- [claimed-docs] “create a Pod per customer, give them a scoped API key, and route webhook events to the right place.”
- [claimed-docs] “Scoped API keys restrict access to a single pod or a single inbox.”
- [claimed-docs] “`Permissions` let you restrict what an API key can do.”
- [claimed-docs] “Create one pod per customer/tenant in your system”
ai-native userBuild against official SDKs
weight 2 · round to AgentMailShortwavenone0/10No evidence of any official SDKs for developers; probes for llms.txt, docs.md, and OpenAPI/swagger specs all returned 404, and the evidence pack only documents MCP-based integrations for end-user workflows (Slack, Notion, Zapier) rather than a developer SDK.
AgentMail is fundamentally an API-first product with dedicated docs, OpenAPI spec, quickstart showing API key/SDK registration, and popovers showing SDK examples praised by a community reviewer, confirming real SDK-based building. Missing for 10: explicit list of language-specific SDKs (e.g. Python/TS/Go) and independent third-party developer testimonials beyond the dashboard praise.
- [claimed-docs] “The agent registers itself using the human email you provide and gets back an API key, inbox ID, and organization ID.”
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.agentmail.to/openapi.json — contains "openapi" key”
- [community] “What I am most impressed by is the popovers in your dashboard, which show SDK examples. This is a brilliant UI idea (executed with great pol…”
ai-native userSubscribe to events via webhooks
weight 2 · round to AgentMailShortwavenone0/10Shortwave's evidence covers triggers, MCP integrations, and Zapier connections, but nothing describes outbound webhooks that let an AI-native user subscribe to Shortwave events; no webhook API, subscription endpoint, or event schema is documented, and OpenAPI/llms.txt probes returned 404s.
- [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
- [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
AgentMail's docs explicitly support webhook subscriptions: registering a URL to receive POST requests on email events instead of polling, avoiding the need for constant API checks. This is a first-party documented, core feature directly matching the story. Missing for 10: independent/hands-on confirmation that webhooks work reliably in practice.
- [claimed-docs] “Instead of constantly asking the AgentMail API if there's a new email (a process called polling), you can register a URL, and we will send y…”
- [claimed-docs] “you can register a URL, and we will send you a `POST` request with the details as soon as an event happens.”
Agentic features
ai-native userSet up automations that run autonomously in the background
weight 2 · round to ShortwaveShortwave explicitly supports triggers that draft replies, add comments, organize threads into todos when emails arrive, plus custom AI filters running as background scripts and Tasklet integration to auto-act on emails—these run autonomously without user initiation. However, evidence is all vendor-sourced with no independent verification of reliability or scope of autonomy. Missing for 10: independent/hands-on confirmation of trigger reliability, detail on trigger configuration UI, and evidence of complex multi-step autonomous workflows beyond simple triggers.
- [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”
- [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
- [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”
AgentMail provides the building blocks for background automation—webhooks and persistent WebSocket connections that push email events in real time instead of requiring polling—so an agent can react autonomously to inbound mail without a human in the loop. However, AgentMail itself is just email infrastructure; there's no evidence of a built-in scheduler, workflow engine, or persistent agent runtime that executes autonomous logic—that has to be built by the user on top of the webhook/websocket feed. Missing for 10: evidence of a native scheduling/automation engine, documented autonomous background job execution, or independent confirmation that these mechanisms reliably drive unattended agent workflows.
- [claimed-docs] “Instead of constantly asking the AgentMail API if there's a new email (a process called polling), you can register a URL, and we will send y…”
- [claimed-docs] “you can register a URL, and we will send you a `POST` request with the details as soon as an event happens.”
- [claimed-docs] “WebSockets provide a persistent, bidirectional connection to AgentMail for receiving email events in real-time.”
- [claimed-docs] “WebSockets don't require a public URL or external tools like ngrok.”
ai-native userOperate the product with natural-language commands
weight 2 · round to ShortwaveShortwave's AI Assistant lets users operate the inbox via natural language—reading threads, writing drafts, searching email history, checking calendar, and running custom AI filters written in plain English—directly in the product's core value proposition. Docs consistently describe this as the primary UX (chat-based assistant, plain-English filter scripts, natural-language triggers). missing for 10: independent/hands-on verification specifically of the natural-language command interface's reliability (community evidence focuses on UI/pricing/privacy, not NL command execution quality).
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
- [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”
- [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
- [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
AgentMail exposes a hosted MCP server with inbox/message/thread/draft tools that lets any MCP-compatible AI agent operate the product via natural language, and also ships a CLI for no-code operations. However, there's no first-party chat/NL interface of its own, nor independent evidence of successful natural-language operation in practice. Missing for 10: hands-on demonstration of natural-language command execution, a dedicated conversational UI beyond MCP tool-calling.
- [claimed-docs] “AgentMail runs a hosted MCP server at https://mcp.agentmail.to/mcp that exposes inbox, message, thread, draft, and attachment tools to any c…”
- [claimed-docs] “AgentMail runs a hosted MCP server at `https://mcp.agentmail.to/mcp` that exposes inbox, message, thread, draft, and attachment tools to any…”
- [claimed-docs] “Create inboxes, send messages, manage threads, and more — all without writing code.”
- [probe] “official MCP server documented at https://docs.agentmail.to/integrations/mcp”
- [probe] “official CLI documented at https://docs.agentmail.to/integrations/cli”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to AgentMailShortwavenone0/10Shortwave is an email client, not a developer platform with an API reference; probes for llms.txt, docs.md, and OpenAPI specs all returned 404s, and no evidence mentions any interactive API documentation or runnable code examples.
AgentMail exposes a machine-readable OpenAPI spec (agentmail-probe-2) and its docs site includes language-switchable code snippets (Python/curl) plus SDK example popovers praised by users (agentmail-comm-2, agentmail-comm-7), suggesting an interactive reference. However, there is no evidence of a true 'try it now' runnable/executable API console, and independent reports note the docs site itself is slow and glitchy (agentmail-comm-1, agentmail-comm-3), undermining a smooth interactive experience. Missing for 10: confirmation of an actual runnable/sandboxed request execution feature, and resolution of the reported performance/UX issues on the docs site.
- [probe] “PROBE openapi: HTTP 200 at https://docs.agentmail.to/openapi.json — contains "openapi" key”
- [community] “The website is really bad. Moving from Python to curl tab on the site shows noticeable lag - I have seen 2-3 whole websites load faster in t…”
- [community] “What I am most impressed by is the popovers in your dashboard, which show SDK examples. This is a brilliant UI idea (executed with great pol…”
- [community] “"Application error: a client-side exception has occurred while loading www.agentmail.to"... Failed to create WebGL context... Cookie rejecte…”
- [community] “I have written about how slow the website is... the amount of lag is something I have genuinely never witnessed in any website... I can't vi…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to AgentMailShortwavenone0/10Direct probes for OpenAPI/swagger specs and llms.txt all returned 404s, and no docs mention a machine-readable API spec.
A probe confirms the OpenAPI spec is live and machine-readable at https://docs.agentmail.to/openapi.json (HTTP 200, contains "openapi" key), backed by documented API-first design. Missing for 10: no independent third-party corroboration of spec completeness or SDK auto-generation from it.
- [probe] “PROBE openapi: HTTP 200 at https://docs.agentmail.to/openapi.json — contains "openapi" key”
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnShortwavenone0/10No evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI/llms.txt/docs endpoints all returned 404s, and no docs mention versioned APIs.
Ai email — stories about ai email in this arenaAi email
Stories about ai email in this arena
Agent workflows
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 to AgentMailShortwavenone0/10Shortwave documents an internal AI Assistant that reads/drafts/searches email, and it can act as an MCP *client* connecting its own AI to external apps (Slack, GitHub, Zapier, etc.), but there is no evidence Shortwave exposes itself as an MCP server or documented API that lets an external agent (Claude, ChatGPT, or a custom agent) read/triage/draft/send mail through it. Probes confirm no llms.txt, no docs.md, and no OpenAPI/Swagger endpoint, indicating no documented external-agent connection surface.
- [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
- [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
- [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
- [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
AgentMail documents a hosted MCP server exposing inbox, message, thread, draft, and attachment tools, plus a full API/CLI for creating inboxes, reading/searching threads, drafting (with human-in-the-loop review), and sending messages with attachments — enabling any MCP-compatible agent (Claude, ChatGPT, custom) to triage and send email end to end. missing for 10: independent hands-on verification of an external agent completing a full read-triage-send workflow via the MCP connection (only vendor docs and probes confirm the endpoint, no third-party usage report).
- [claimed-docs] “AgentMail runs a hosted MCP server at https://mcp.agentmail.to/mcp that exposes inbox, message, thread, draft, and attachment tools to any c…”
- [claimed-docs] “AgentMail runs a hosted MCP server at `https://mcp.agentmail.to/mcp` that exposes inbox, message, thread, draft, and attachment tools to any…”
- [probe] “official MCP server documented at https://docs.agentmail.to/integrations/mcp”
- [claimed-docs] “Human-in-the-Loop Review: An agent can create a `Draft` for a sensitive or important `Message`, which a human can then review and approve be…”
- [claimed-docs] “To start a new conversation, you can send a Message from one of your inboxes.”
- [claimed-docs] “Full-text search finds Threads by keyword across the sender, recipients, subject, and message body, ranked by relevance.”
- [claimed-docs] “Your agents can both send `Attachments` in outgoing `Messages` and process `Attachments` from incoming `Messages`.”
- [claimed-docs] “You can cc or bcc a real person on any message your agent sends, creating a "human-in-the-loop" workflow for oversight, escalations, or qual…”
Ai assistant
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 ShortwaveDocs directly describe the AI Assistant reading threads, writing drafts, searching entire email history, and checking calendar — matching the grounded cross-inbox/calendar Q&A story. Community evidence corroborates fast search/summaries and real usage, though no independent hands-on confirmation of complex multi-thread grounded reasoning exists. Missing for 10: independent hands-on verification of accuracy/groundedness across large inboxes, and detail on how calendar+email context are combined in answers.
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
- [claimed-docs] “Instant Summaries show up at the very top of your email threads the instant you open them.”
- [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”
AgentMailnone0/10AgentMail is developer infrastructure (an email API/MCP server) for building agent-driven email workflows, not an end-user assistant that answers grounded questions across inbox and calendar. Evidence shows full-text search across threads and MCP tool exposure (docs-5, docs-12), but there is no calendar integration anywhere in the evidence, and no shipped assistant/chat interface that synthesizes 'who said what' or 'what's outstanding' answers for a user.
- [claimed-docs] “Full-text search finds Threads by keyword across the sender, recipients, subject, and message body, ranked by relevance.”
- [claimed-docs] “AgentMail runs a hosted MCP server at https://mcp.agentmail.to/mcp that exposes inbox, message, thread, draft, and attachment tools to any c…”
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
Ai drafting
ai-native userAI drafts replies in my own voice and tone — ready to review and send, not generic boilerplate
weight 3 · round to ShortwaveShortwave's AI Assistant explicitly 'writes drafts' and Ghostwriter autocompletes replies as you type, confirming AI-drafted replies are a core capability. However, no evidence specifically shows the AI learns or mimics the user's personal voice/tone (vs. generic suggestions or template-based AI Snippets), so the 'own voice' personalization claim is unverified. Missing for 10: explicit documentation of voice/tone personalization or learning from user's writing style, and independent user reports confirming drafts sound authentically like them rather than generic AI text.
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
- [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete.”
- [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete”
- [claimed-docs] “AI Snippets let you define an email template once upfront and then re-use it whenever you need it.”
AgentMailnone0/10AgentMail provides Draft objects and human-in-the-loop review (an agent can create a Draft for a human to approve before sending), but there is no evidence that AgentMail itself learns or applies the user's personal voice/tone when generating drafts — it is an email infrastructure/API for agents, not a personalization/writing-style engine.
- [claimed-docs] “Human-in-the-Loop Review: An agent can create a `Draft` for a sensitive or important `Message`, which a human can then review and approve be…”
- [claimed-docs] “You can cc or bcc a real person on any message your agent sends, creating a "human-in-the-loop" workflow for oversight, escalations, or qual…”
Ai triage
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 ShortwaveShortwave ships custom AI filters that auto-label, star, and archive using plain-English scripts, plus Bundles/Splits to categorize inbox by importance and one-click identification of important emails/todos, directly matching the triage story; community feedback corroborates the bundling/importance-sorting feature as effective ('top shelf'). Steerability is evidenced via the plain-English filter scripts, but missing for 10: explicit audit-trail/log of AI triage decisions and independent verification of filter reliability at scale.
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”
- [claimed-docs] “They’re a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
- [claimed-docs] “Splits let you handle different types of emails at different times, so you can stay responsive where it matters most.”
- [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”
AgentMailnone0/10AgentMail provides developer primitives (Labels, Lists, full-text search, webhooks) that a developer could use to build inbox triage, but there is no evidence of AgentMail itself performing AI-driven auto-labeling, categorization, or surfacing-what-needs-attention out of the box — Labels are described as manually tracked conversation states, not an automated triage engine, and no docs describe a built-in AI classifier or steerable/auditable triage policy.
- [claimed-docs] “Use `Labels` to track the state of a conversation.”
- [claimed-docs] “`Lists` allow you to filter emails by allowing or blocking specific email addresses or domains.”
- [claimed-docs] “Full-text search finds Threads by keyword across the sender, recipients, subject, and message body, ranked by relevance.”
- [claimed-docs] “Instead of constantly asking the AgentMail API if there's a new email (a process called polling), you can register a URL, and we will send y…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to ShortwaveShortwave's custom AI filters ('automatically label, star, archive, and more with scripts you write in plain English') and one-click sweep of non-important emails/todos (docs-15, docs-29) directly support automated actions applied across many inbox items at once, and triggers (docs-1) extend this to organizing threads into todos in bulk. However, there's no explicit documentation of a true multi-select bulk-action UI, batch limits, or independent hands-on confirmation that these AI filters reliably scale across large volumes of email. Missing for 10: explicit bulk-select/apply workflow docs, scale/performance evidence, and independent user corroboration of bulk automation working as advertised.
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”
- [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
Docs confirm the platform is fully API-driven and explicitly supports creating 'tens, hundreds, or even thousands' of inboxes on demand, implying agents can script bulk creation, but there's no documented dedicated bulk/batch endpoint for messages, threads, or other items (e.g., bulk send, bulk label, bulk delete). Missing for 10: dedicated batch/bulk API endpoints for messages/threads, documented rate-limit or batching guidance, hands-on evidence of bulk operations at scale.
- [claimed-docs] “You can create tens, hundreds, or even thousands of Inboxes for your agents on demand.”
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
- [claimed-docs] “Create inboxes, send messages, manage threads, and more — all without writing code.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to ShortwaveShortwave documents explicit rule/trigger automation: triggers that draft replies when emails arrive, custom AI filters written in plain English that auto-label/star/archive, and Tasklet integration that takes automatic actions on emails as they arrive. This directly matches defining rules that fire on events (email arrival) with automated actions. Missing for 10: independent/hands-on verification that these triggers work reliably in practice, and more detail on rule complexity/limits beyond marketing copy.
- [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”
AgentMail exposes event-driven infrastructure (webhooks and websockets) so external code can react to inbox events, and Lists provide simple automatic allow/block rules on senders/domains, but there's no built-in rule engine for defining conditional 'if X then do Y' automations inside the product itself — the actual rule logic must be implemented by the developer/agent consuming the webhook. missing for 10: a native rules/automation engine (e.g. conditional triggers on subject/content beyond allow-block lists), and independent confirmation that webhook-driven automation works reliably in production.
- [claimed-docs] “Instead of constantly asking the AgentMail API if there's a new email (a process called polling), you can register a URL, and we will send y…”
- [claimed-docs] “you can register a URL, and we will send you a `POST` request with the details as soon as an event happens.”
- [claimed-docs] “WebSockets provide a persistent, bidirectional connection to AgentMail for receiving email events in real-time.”
- [claimed-docs] “`Lists` allow you to filter emails by allowing or blocking specific email addresses or domains.”
- [claimed-docs] “Use `Labels` to track the state of a conversation.”
Composing sending — stories about composing sending in this arenaComposing sending
Stories about composing sending in this arena
Sending
power-userSee whether and when recipients opened my email
weight 1 · round drawnShortwavenone0/10No evidence in the pack mentions read receipts, open tracking, or notifications about recipient email opens; Shortwave's documented features cover AI drafting, snippets, scheduling, undo send, and integrations but nothing about tracking whether/when recipients opened a message.
power-userSchedule an email to send later and undo a send within a grace window
weight 2 · round to ShortwaveShortwave's docs explicitly describe both scheduled send (set a time, write message, move on) and undo send (revert a sent message back to a draft), directly matching the story. Missing for 10: explicit detail on the undo grace-window duration and independent/hands-on corroboration beyond vendor blog.
- [claimed-docs] “Scheduled send gives you the ability to send an email at a future time.”
- [claimed-docs] “Undo send staves off the panic you feel when you accidentally send a message that wasn't ready by allowing you to revert a sent message back…”
- [claimed-docs] “Scheduled send gives you the ability to send an email at a future time. All you have to do is write a message, set a send time, and then mov…”
Templates
power-userInsert saved snippets or templates — with variables and attachments — instead of retyping the same reply
weight 2 · round to ShortwaveShortwave documents 'AI Snippets' that let users define an email template once and reuse it, available for individual and team use — directly matching the core snippet/template story. However, the evidence never confirms support for variables (dynamic fields) within snippets or attaching files as part of a snippet, both explicitly requested in the story. Missing for 10: documentation of variable/placeholder support in snippets, documentation of attachment bundling with snippets, and independent/hands-on confirmation of the feature working as described.
- [claimed-docs] “AI Snippets let you define an email template once upfront and then re-use it whenever you need it.”
- [claimed-docs] “AI Snippets are available both for individual use and for use across your team.”
AgentMailnone0/10AgentMail is an API/infrastructure product for agent-driven email (inboxes, messages, drafts, attachments, webhooks) with no evidence of a saved snippets/templates library or variable-substitution feature for composing replies; nothing in the docs mentions reusable templates or canned responses.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to AgentMailShortwavenone0/10No evidence of a public API for Shortwave; probes for llms.txt, docs-md, and OpenAPI specs all returned 404, and no documentation mentions programmatic access to core features like AI assistant, triggers, or inbox management outside the UI/MCP integration (which is inbound, not an outbound API for replicating UI actions).
AgentMail is explicitly API-first ('Create, manage, and operate email inboxes entirely via API'), with a documented OpenAPI spec, CLI, and MCP server all built atop the same API surface (inboxes, messages, threads, drafts, webhooks, attachments, permissions, pods) — no UI-exclusive features are mentioned anywhere in the docs. missing for 10: an explicit statement or independent test confirming 1:1 parity between the dashboard UI and API (e.g., that every dashboard action maps to a documented endpoint).
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.agentmail.to/openapi.json — contains "openapi" key”
- [claimed-docs] “Create inboxes, send messages, manage threads, and more — all without writing code.”
- [probe] “official CLI documented at https://docs.agentmail.to/integrations/cli”
- [claimed-docs] “create a Pod per customer, give them a scoped API key, and route webhook events to the right place.”
- [claimed-docs] “Scoped API keys restrict access to a single pod or a single inbox.”
- [claimed-docs] “`Permissions` let you restrict what an API key can do.”
ai-native userExport all of my data in open formats and leave
weight 3 · round to AgentMailShortwavenone0/10No evidence of any data export feature (mailbox, comments, snippets, etc.) in open formats; probes for llms.txt, docs-md, and openapi endpoints all returned 404, and no changelog/blog mentions an export or account-portability capability. Community threads mention deleting the account making it 'low-risk' to switch back to Gmail, but that is because Shortwave uses Gmail as the underlying store, not because Shortwave itself offers a data export mechanism. missing for 10: any documented export/download feature, supported open file formats, or migration/backup tooling.
- [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
- [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”
AgentMail supports connecting standard IMAP/SMTP clients (Outlook, Thunderbird, Apple Mail), which gives users open-protocol access to their mailbox data rather than lock-in to a proprietary format, and the OpenAPI spec/CLI allow programmatic retrieval of messages. However there is no explicit documented 'export all data' or account-portability/data-takeout feature, and no evidence of exporting threads/attachments in bulk open formats. Missing for 10: explicit bulk export/backup tooling, documented data-portability guarantees, and confirmation of full account deletion with data takeout.
- [claimed-docs] “Connect Outlook, Thunderbird, Apple Mail, or any IMAP/SMTP-compatible client to your AgentMail inbox”
- [probe] “PROBE openapi: HTTP 200 at https://docs.agentmail.to/openapi.json — contains "openapi" key”
- [claimed-docs] “Create inboxes, send messages, manage threads, and more — all without writing code.”
ai-native userRead the product's source under an open license
weight 2 · round drawnShortwavenone0/10No evidence of any open-source license or public source repository for Shortwave; it is a closed commercial SaaS email client with no mention of open licensing anywhere in the evidence pack.
ai-native userSelf-host the core product
weight 3 · round drawnShortwavenone0/10Shortwave is a hosted SaaS email client with no evidence of any self-hostable version; it relies on Google servers and its own cloud infrastructure (comm-11), and no self-hosting docs, Docker images, or open-source releases exist in the evidence pack.
- [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
- [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
AgentMailnone0/10AgentMail is presented entirely as a hosted API/SaaS product (docs describe hosted MCP server, hosted API, dashboards) with no documentation of a self-hosted deployment option; a community comment even notes a competitor markets itself as 'a self-hosted drop-in replacement' for AgentMail, implying AgentMail itself lacks this capability.
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
- [claimed-docs] “AgentMail runs a hosted MCP server at https://mcp.agentmail.to/mcp that exposes inbox, message, thread, draft, and attachment tools to any c…”
- [community] “agentmail charges $20/mo for 10 inboxes. autopilot gives you unlimited inboxes for the cost of a postgres row, positioning itself as a self-…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnShortwavenone0/10No evidence anywhere in the pack mentions data residency, region selection, or storage location controls; Shortwave is shown to run on Google servers with no configurable region options, and community comments only raise general privacy/security concerns without any residency feature being offered.
- [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
- [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnShortwavenone0/10No evidence pack item describes any setting, policy statement, or opt-out mechanism letting users prevent their email/AI data from being used for model training; the only related community evidence (shortwave-comm-7) actually flags that Shortwave's privacy policy permits sharing email content/metadata with third-party vendors, which a user rejected outright rather than confirming a training opt-out exists.
- [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
- [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
ai-native userControl data retention and deletion
weight 2 · round to ShortwaveThe only evidence touching on data deletion is a community anecdote that deleting one's Shortwave account makes it low-risk to switch back to Gmail, implying account-level deletion works, but there is no documented retention policy, granular deletion controls, or data-lifecycle settings; community comments even flag privacy concerns about email content being synced/shared with third-party vendors with no denylist option. missing for 10: documented retention policy, explicit deletion/export controls, first-party privacy/data-handling documentation.
- [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”
- [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
- [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnShortwavenone0/10No evidence Shortwave offers any telemetry/usage-tracking opt-out control; documentation focuses on AI features and integrations, and community discussion instead raises concerns about email content being shared with third-party vendors with no denylist option, but nothing addresses telemetry/analytics opt-out specifically.
- [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
- [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
Search history — stories about search history in this arenaSearch history
Stories about search history in this arena
Search
power-userSearch is fast and precise — operators, filters, and ranked results across my full mail history
weight 2 · round to AgentMailShortwavedisputedcontradicted4/10Shortwave's AI assistant is documented to 'search your entire email history' (shortwave-docs-12/28), but community evidence shows the free plan doesn't import emails older than 90 days before signup for search, contradicting the 'full mail history' claim, and no evidence describes search operators, advanced filters, or ranked-result mechanics. Missing for 10: documented search operators/filters syntax, ranking algorithm details, confirmation that paid tiers truly cover unlimited history without caveats.
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
- [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”
Docs confirm full-text search across sender, recipients, subject, and body with relevance ranking, covering the core 'ranked results' and 'across full mail history' aspects. However, there's no evidence of specific search operators (e.g., date ranges, boolean logic) or advanced filters, and no independent benchmarking of speed/precision. missing for 10: documented search operators/filters syntax, evidence of performance at scale, independent verification of search speed/precision.
- [claimed-docs] “Full-text search finds Threads by keyword across the sender, recipients, subject, and message body, ranked by relevance.”
Speed keyboard — stories about speed keyboard in this arenaSpeed keyboard
Stories about speed keyboard in this arena
Shortcuts
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 drawnShortwavenone0/10The evidence pack contains no mentions of keyboard shortcuts, a command palette, or performance/speed benchmarks — all citations focus on AI features, integrations, and collaboration tools. Absence of evidence for this applicable axis (email clients commonly tout keyboard-driven UX, e.g. Superhuman comparisons appear in community items) yields 'none' rather than 'na'.
AgentMailnone0/10AgentMail's docs focus entirely on API/SDK/CLI/webhook/MCP functionality for building agent email workflows; there is no mention anywhere of keyboard shortcuts, a command palette, or any interactive UI navigation features for power users. Community evidence actually describes the dashboard/website as laggy and slow to load (WebGL errors, noticeable lag vs. other sites), directly undercutting the 'fast enough to never wait' requirement even if such an interface existed.
- [community] “"Application error: a client-side exception has occurred while loading www.agentmail.to"... Failed to create WebGL context... Cookie rejecte…”
- [community] “The website is really bad. Moving from Python to curl tab on the site shows noticeable lag - I have seen 2-3 whole websites load faster in t…”
- [community] “I have written about how slow the website is... the amount of lag is something I have genuinely never witnessed in any website... I can't vi…”
- [claimed-docs] “Create inboxes, send messages, manage threads, and more — all without writing code.”
Team collaboration — stories about team collaboration in this arenaTeam collaboration
Stories about team collaboration in this arena
Shared inbox
team-leadMy team works shared inboxes together — shared accounts or team channels where everyone sees the same conversation state
weight 3 · round to ShortwaveShortwave offers team comments and @mention that grant teammates access to specific emails/threads (shortwave-docs-10,11,34,37), enabling some shared visibility and discussion. However, community evidence explicitly questions whether Shortwave's 'Bundles'/Workspaces model can replace true shared/team inboxes as found in dedicated tools (shortwave-comm-4), and there is no direct documentation of a shared-account or team-channel inbox where the whole team sees identical conversation state by default. Missing for 10: explicit shared-inbox/team-channel product feature, documentation of multi-user access to a single mailbox, and confirmation that collaboration extends beyond per-email comments to full inbox-level shared state.
- [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
- [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
- [claimed-docs] “Something special happens when you @mention a teammate in a comment – they suddenly get access to not just your comment, but the email too”
- [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave”
- [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”
AgentMailnone0/10AgentMail's docs describe agent-centric inboxes, cc/bcc human-in-the-loop oversight, drafts for approval, and per-tenant Pods, but nothing indicates a shared inbox/team-channel experience where multiple human team members view the same conversation state together. No evidence of shared inbox dashboards, team member roles, or collaborative conversation views for a team-lead's team.
- [claimed-docs] “You can cc or bcc a real person on any message your agent sends, creating a "human-in-the-loop" workflow for oversight, escalations, or qual…”
- [claimed-docs] “create a Pod per customer, give them a scoped API key, and route webhook events to the right place.”
- [claimed-docs] “Human-in-the-Loop Review: An agent can create a `Draft` for a sensitive or important `Message`, which a human can then review and approve be…”
- [claimed-docs] “Use `Labels` to track the state of a conversation.”
- [claimed-docs] “Create one pod per customer/tenant in your system”
Triage inbox — stories about triage inbox in this arenaTriage inbox
Stories about triage inbox in this arena
Inbox structure
power-userSelect many conversations at once and archive, label, or mark them done in one stroke
weight 1 · round to ShortwaveShortwave's docs mention bulk-oriented behaviors—custom AI filters that automatically label/star/archive matching emails, and a one-click 'sweep away the rest' declutter action—that imply multi-conversation bulk actions, but there is no explicit mention of manually multi-selecting conversations and applying archive/label/mark-done in one stroke. Missing for 10: explicit multi-select UI documentation, confirmation that labels/archive/done can be applied simultaneously to a manual selection, and independent/hands-on confirmation of this specific workflow.
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”
AgentMailnone0/10AgentMail's docs describe programmatic labeling, threading, and search, but there is no evidence of any UI or bulk API operation for selecting many conversations at once and archiving/labeling/marking done in a single action; the product is positioned as an agent-facing API rather than a human triage inbox with bulk controls.
- [claimed-docs] “Use `Labels` to track the state of a conversation.”
- [claimed-docs] “Full-text search finds Threads by keyword across the sender, recipients, subject, and message body, ranked by relevance.”
Not comparable on these axes
switcherConnect several accounts across providers — Gmail, Microsoft 365, IMAP — and work them from one place
weight 3 · not comparableShortwavenone0/10No evidence Shortwave supports connecting multiple providers (Gmail, Microsoft 365, IMAP) from one inbox; in fact the founder explicitly states they integrate only with Gmail's APIs ('not IMAP'), and a user confirms 'it only works with Google servers.' This directly contradicts the multi-provider switcher story rather than merely lacking support for it.
- [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”
- [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
AgentMailn/aAgentMail is a developer API for provisioning and operating new email inboxes for AI agents, not a personal multi-account client for consolidating existing Gmail/Microsoft 365/IMAP accounts. Its IMAP/SMTP feature runs the opposite direction — letting external clients connect INTO an AgentMail-created inbox — not aggregating a switcher's pre-existing provider accounts into one interface, so the 'switcher consolidating accounts' story is a category mismatch for this product.
- [claimed-docs] “Connect Outlook, Thunderbird, Apple Mail, or any IMAP/SMTP-compatible client to your AgentMail inbox”
- [claimed-docs] “Create, manage, and operate email inboxes entirely via API.”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableShortwave explicitly documents connecting to any MCP server via 'Add custom integration' to let its AI Assistant use those tools, with first-party blog docs and pricing page confirming MCP support alongside built-in integrations. Missing for 10: independent hands-on verification of the MCP setup flow and no detail on tool-call reliability/limits beyond marketing docs.
- [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
- [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
- [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
- [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
- [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
- [community] “Security vendor blog highlighted that Shortwave's AI Email with MCP integration 'opens up rich capabilities—but also new attack surfaces,' f…”
AgentMailn/aAgentMail is an email infrastructure/API product for agents, not itself an agentic runtime that consumes external tools. Its only MCP-related capability is hosting its own MCP server so other agents can call AgentMail's tools (docs-12/23), not acting as an MCP client that plugs in third-party MCP servers — so this client-side story is a category error for this product.
- [claimed-docs] “AgentMail runs a hosted MCP server at https://mcp.agentmail.to/mcp that exposes inbox, message, thread, draft, and attachment tools to any c…”
- [claimed-docs] “AgentMail runs a hosted MCP server at `https://mcp.agentmail.to/mcp` that exposes inbox, message, thread, draft, and attachment tools to any…”
- [probe] “official MCP server documented at https://docs.agentmail.to/integrations/mcp”
ai-native userUse an official CLI
weight 2 · not comparableShortwaven/aShortwave is an AI email client product, not a developer tool/platform where an official CLI is a natural offering; no evidence suggests it ships or intends a CLI, and the product's interaction model is web/app-based with MCP integrations rather than command-line workflows.
AgentMail documents an official CLI (docs.agentmail.to/integrations/cli) that lets users create inboxes, send messages, and manage threads without writing code, corroborated by a probe confirming the page exists. Missing for 10: no independent/community hands-on confirmation of CLI usage or installation details beyond the docs themselves.
- [claimed-docs] “Create inboxes, send messages, manage threads, and more — all without writing code.”
- [probe] “official CLI documented at https://docs.agentmail.to/integrations/cli”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableShortwave delivers AI-generated insights directly in-product: Instant Summaries appear atop threads, AI Assistant reads threads/searches history/checks calendar to surface answers, Ghostwriter offers inline autocomplete suggestions, and custom AI filters/triggers auto-label and organize emails based on AI analysis. These are well-documented first-party features spanning summarization, suggestion, and automated insight generation across the inbox. Missing for 10: independent hands-on validation of insight quality/accuracy and no third-party review confirming these AI insights work reliably in practice beyond vendor claims.
- [claimed-docs] “Instant Summaries show up at the very top of your email threads the instant you open them.”
- [claimed-docs] “Instant Summaries show up at the very top of your email threads the **instant** you open them.”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
- [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete.”
- [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete”
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”
AgentMailn/aAgentMail is an email infrastructure API for AI agents, not an analytics/insights product; the evidence shows email inbox/message/thread management, search, and MCP/CLI integrations but no AI-generated insights or suggestions surfaced from user data. This story is a category error for an email API product.
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableShortwave has a built-in AI assistant/executive assistant that can read threads, write drafts, search email history, check calendar, run custom AI filters, and take multi-step actions via triggers and MCP integrations without leaving the inbox — clearly delegatable task execution. Missing for 10: independent hands-on validation of end-to-end delegated task completion (beyond vendor blog claims) and details on reliability/error handling.
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
- [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”
- [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
- [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”
AgentMailn/aAgentMail is an email infrastructure/API product for building AI agents that use email, not a product with its own built-in AI assistant to delegate tasks to. The 'delegate tasks to a built-in AI assistant' axis is a category error here—AgentMail provides the plumbing (inboxes, MCP tools, webhooks) for external agents to use, but does not itself ship an assistant a user converses with.
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableShortwaven/aShortwave is an AI-native email client, not a developer platform or API product; there is no concept of a sandbox vs. production environment for testing in this context, so this axis is a category error for this product type.
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableShortwave offers event-based 'triggers' (auto-draft replies, add comments, organize todos) and custom AI filters that run automatically in plain English, which are a form of automation, but these are reactive triggers on incoming events rather than true time-based recurring/scheduled jobs — the only scheduling feature documented (Scheduled Send) is a one-time future send, not a recurring workflow. Missing for 10: explicit recurring/cron-style scheduling of AI workflows, documentation of periodic digest or repeat-interval automations, and independent confirmation that triggers can run on a time-based recurring cadence rather than only on email arrival.
- [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [claimed-docs] “Scheduled send gives you the ability to send an email at a future time.”
- [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”
AgentMailn/aAgentMail is an email infrastructure/API product for agents (inboxes, messages, webhooks, MCP tools), not a workflow/job scheduling or automation-orchestration platform; scheduling recurring jobs is outside its product category and would be handled by an external orchestrator consuming its API.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableShortwavenone0/10Shortwave offers AI filters, triggers, and MCP integrations for automation, but there is no evidence of version history, review workflows, diffs, or rollback capability for these automations.
AgentMailn/aAgentMail is an email API/infrastructure product for AI agents, not an automation-authoring platform with a build/version history; versioning, reviewing, and rolling back 'automations' is not a coherent concept for this product's category — it has no workflow/automation builder to version or roll back.
power-userSee my calendar, respond to invites, and create events without leaving the email client
weight 2 · not comparableShortwave's AI assistant is documented to 'check your calendar' and integrate with Calendar as one of many connected apps, implying some calendar visibility inside the client, but there is no evidence of responding to invites or creating events without leaving the email client. missing for 10: explicit calendar view/UI, invite RSVP handling, and event-creation workflow evidence.
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
- [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
- [claimed-docs] “Connect the AI to your Slack, Calendar, Notion, Asana, Hubspot, and more so you can automate workflows without ever leaving your inbox.”
AgentMailn/aAgentMail is an email API/infrastructure product for AI agents, not a calendar or email client with a UI for viewing calendars or invites; the evidence only covers inbox/message/thread APIs, webhooks, MCP, and CLI tooling, with no calendar functionality mentioned. This is a category mismatch, not a missing feature.
power-userShare my availability or insert bookable meeting times directly into an email
weight 1 · not comparableShortwavenone0/10Evidence shows Shortwave's AI can 'check your calendar' and connect to Calendar via integrations, but there is no mention of sharing availability or inserting bookable meeting time slots into an email — a distinct calendar-scheduling feature not evidenced anywhere in the pack.
AgentMailn/aAgentMail is an email API/infrastructure product for AI agents to send/receive messages; it has no calendar or scheduling/availability features. Sharing availability or inserting bookable meeting times is a calendar-integration capability entirely outside its product category (email inbox management, not scheduling).
power-userRead, search, and write email offline, with changes syncing when I reconnect
weight 2 · not comparableThe founder states Gmail API integration enables 'offline handling' alongside real-time sync, implying some offline capability, but there's no detail on offline search, offline composing, or how changes reconcile on reconnect. missing for 10: documentation of offline read/search functionality, offline draft writing, and sync-conflict resolution behavior.
- [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”
switcherUse aliases or masked addresses so sign-ups and strangers never learn my real address
weight 1 · not comparableShortwavenone0/10No evidence Shortwave offers email aliasing, masked addresses, or similar identity-protection features for sign-ups; the pack only covers AI assistant, integrations, and inbox management features unrelated to address masking.
AgentMailn/aAgentMail is a developer infrastructure product for giving AI agents email identities and inboxes, not a consumer privacy/alias-masking service for humans hiding their real address from sign-ups and strangers; the entire evidence pack is about agent inbox provisioning, APIs, webhooks, and multi-tenancy for building agent products, not personal alias/masked-address privacy protection.
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 · not comparableShortwavenone0/10No evidence anywhere in the pack describes Shortwave blocking sender tracking pixels, nor does it detail transparent data-handling practices for mail content; the only related community evidence (comm-6, comm-7) actually raises unaddressed privacy concerns about syncing sensitive mail and sharing content/metadata with third-party vendors. missing for 10: any mention of read-pixel/tracking-pixel blocking, any transparency documentation on mail data handling, and evidence rebutting the third-party data-sharing concerns.
- [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
- [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
AgentMailn/aAgentMail is an email API/infrastructure product for AI agents, not a consumer email client that a 'switcher' persona would adopt to protect against sender tracking pixels; the story's framing (client-side anti-tracking, pixel blocking) is a wrong axis for this developer-facing API product.
switcherImport my complete mail history and contacts from my old provider or client
weight 1 · not comparableShortwave is built directly on Gmail's APIs, so it can pull in an existing Gmail account's aliases and signatures (one user reported it 'imported all my aliases and signatures' during onboarding), but this is only a Gmail-to-Shortwave migration, not import from another provider/client like Outlook or Yahoo — a security-focused user explicitly noted 'it only works with Google servers.' Additionally, a documented free-plan limitation caps historical search import at 90 days, undercutting 'complete mail history.' Missing for 10: evidence of contacts import, support for non-Gmail providers, and confirmation that paid plans truly import full history without gaps.
- [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”
- [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”
- [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
- [community] “User complaint: 'all these apps either want gmail way too many gmail permissions, and/or are hosted... I'm trying to get rid of gmail lol.'”
team-leadThe same inbox also handles adjacent customer channels — SMS, WhatsApp, social, or live chat — beside email
weight 1 · not comparableShortwavenone0/10The 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.)
team-leadAssign conversations to teammates and route incoming mail with rules so ownership is explicit
weight 2 · not comparableShortwave offers team comments and @mention to loop teammates into a thread (giving them access to the email) and custom AI filters that can label/archive/star via plain-English rules, but there is no evidence of an explicit 'assign conversation to teammate' ownership feature or rule-based routing of incoming mail to specific team members/inboxes. missing for 10: explicit conversation assignment/ownership feature, mail routing rules tied to teammates, evidence of shared/team inbox queue management.
- [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
- [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
- [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
- [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”
AgentMailn/aAgentMail is an email infrastructure API built for provisioning per-agent inboxes and automating agent-driven email flows, not a human shared-inbox/helpdesk tool with teammate assignment or ownership routing rules. Its team-oriented primitives (Pods, Labels, Lists, scoped API keys) are for tenant/agent segmentation and message-state tracking, not for a team-lead assigning conversations to human teammates.
- [claimed-docs] “create a Pod per customer, give them a scoped API key, and route webhook events to the right place.”
- [claimed-docs] “Use `Labels` to track the state of a conversation.”
- [claimed-docs] “`Lists` allow you to filter emails by allowing or blocking specific email addresses or domains.”
team-leadWe can discuss an email in an internal side-thread — comments and @mentions beside the message — instead of forwarding copies around
weight 2 · not comparableShortwave's Team Comments feature explicitly lets teammates privately discuss an email in-app rather than forwarding, with @mentions that grant the mentioned teammate access to the comment and the email — directly matching the story. Missing for 10: independent/hands-on corroboration of the comment-thread UX beyond vendor blog posts, and detail on comment threading/notification mechanics.
- [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
- [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
- [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave”
- [claimed-docs] “Something special happens when you @mention a teammate in a comment – they suddenly get access to not just your comment, but the email too”
- [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
power-userSnooze conversations and set follow-up reminders that resurface a thread if nobody replies
weight 2 · not comparableCommunity evidence confirms Shortwave has a snooze feature (comm-10 references 'snoozed emails' behavior), implying threads can be snoozed and resurfaced, but no evidence describes a follow-up reminder that resurfaces a thread specifically when nobody replies. Missing for 10: dedicated docs on follow-up/no-reply reminders, evidence of reminder triggers tied to reply detection, and confirmation of default snooze durations or scheduling UI for this specific workflow.
- [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”
power-userSplit my inbox into focused streams — important, team, newsletters, calendar invites — so triage happens in priority order, not arrival order
weight 3 · not comparableShortwave's 'Splits' feature explicitly lets users divide one inbox into multiple focused inboxes by importance/type, each in its own tab, directly matching the triage-by-priority story, and independent community feedback (Front power-user) praised the related 'Bundles' grouping as 'top shelf.' Missing for 10: explicit documentation that the default splits match the exact categories named (team, newsletters, calendar invites) rather than just importance-based tabs, and more independent verification of the feature's real-world triage benefit.
- [claimed-docs] “They’re a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
- [claimed-docs] “They're a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
- [claimed-docs] “Splits let you handle different types of emails at different times, so you can stay responsive where it matters most.”
- [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”
AgentMailn/aAgentMail is a developer-facing email API/infrastructure product for building AI-agent inboxes, not a human-facing email client with a personal triage UI; the story assumes an end-user inbox view split into priority streams, which is a different product category. Labels/Lists exist as programmable primitives an agent developer could use, but there is no evidence of a shipped power-user inbox-triage UI, so this axis doesn't fit the product's role.
- [claimed-docs] “Use `Labels` to track the state of a conversation.”
- [claimed-docs] “`Lists` allow you to filter emails by allowing or blocking specific email addresses or domains.”