Otter.ai vs Fathom

Agent ops

1. ai-native userAn agent can automatically file each meeting's action items into my project tracker (Linear, Jira, Asana) using the product's API, webhooks, or native automations

   weight 2 · round to Otter.ai
   Otter.ai~partialprobed7/10

   Otter explicitly documents sending action items into JIRA and Asana (and other tools) plus a public API/webhooks tier and a live, OAuth-gated MCP server enabling AI agents to pull meeting/action-item data into workflows. However, Linear is never named, no OpenAPI/API spec is discoverable (404s on all probed paths), and API/MCP/native project-tracker automations appear gated to Enterprise plans with no independent hands-on confirmation that action items sync correctly end-to-end. Missing for 10: explicit Linear support, publicly discoverable API schema, and independent verification of the automation actually filing items correctly.

   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Send meeting summaries and action items from Otter to ClickUp to manage everything in one place.”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

   Fathom's REST API, webhooks, and SDKs expose AI-generated action items and meeting data (fathom-docs-22, fathom-docs-45, fathom-docs-28) that an agent could use to push items into a project tracker, and the MCP server lets AI assistants query meeting data directly. However there is no evidence of a native/pre-built Linear, Jira, or Asana integration — only CRM field sync is mentioned as a native automation. Missing for 10: documented native connectors to Linear/Jira/Asana, and any example/template showing action items being filed into a project tracker end-to-end.

   • [claimed-docs] “Webhooks will send your meeting data (optionally including the summary, transcript, and action items) to a URL of your choice.”
   • [claimed-docs] “Create a webhook to receive new meeting content. At least one of `include_transcript`, `include_crm_matches`, `include_summary`, or `include…”
   • [claimed-docs] “AI generated action items”
   • [claimed-docs] “CRM field sync, updating records after meetings automatically”
   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.fathom.ai/mcp returned H…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”

   proof ↗⚑ flag

2. ai-native userAn official MCP server lets Claude or any MCP client query my meetings — search, transcripts, action items — with OAuth, no glue code

   weight 3 · round to Fathom
   Otter.ai~partialprobed7/10

   Otter has an official, live MCP server (mcp.otter.ai) confirmed by a runtime probe returning proper OAuth-gated 401/WWW-Authenticate flow, and docs describe searching meetings, transcripts, action items, and granular permission scoping via Claude/ChatGPT — matching the story closely (otter-docs-16, otter-docs-46, otter-docs-47, otter-docs-35, otter-probe-rt-1, otter-probe-2). However, the same probe notes this MCP/API access is gated to Enterprise workspaces only, meaning many AI-native individual users cannot actually use it without an enterprise contract. Missing for 10: broader/self-serve tier availability, independent third-party (non-vendor) confirmation of the OAuth/query experience beyond the runtime probe, and public documentation of full query capabilities (e.g., exact tool/resource list).

   • [claimed-docs] “Connect Otter.ai meeting transcripts and action items to Claude via MCP. Search, recap, and draft follow-ups without leaving the chat.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [claimed-docs] “Your AI assistant can only access meetings you explicitly authorize”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

   Fathom ships an official hosted MCP server (api.fathom.ai/mcp) documented and installable as an official connector in Claude/ChatGPT via OAuth, with a runtime probe confirming it's live and enforces the MCP OAuth flow (401 + WWW-Authenticate pointing to oauth-protected-resource metadata), matching the story's search/transcript/action-items and no-glue-code OAuth requirements. Missing for 10: independent third-party (non-vendor) hands-on confirmation of query capabilities like search/action-items specifically through the MCP tool surface.

   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [claimed-docs] “Fathom is available as an **official connector** in Claude”
   • [claimed-docs] “Your meeting data, now inside ChatGPT, Claude, and more”
   • [claimed-docs] “claude mcp add fathom -- npx mcp-remote@latest https://api.fathom.ai/mcp”
   • [claimed-docs] “Claude Code supports adding MCP servers directly from the command line.”
   • [claimed-docs] “Connect Fathom to any MCP-compatible tool using the server URL below, then authenticate to access your meeting data.”
   • [probe] “official MCP server documented at https://developers.fathom.ai/mcp-docs/index”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.fathom.ai/mcp returned H…”

   proof ↗⚑ flag

3. ai-native userMy scripts can pull transcripts, summaries, and action items from every meeting through a documented API with self-serve keys

   weight 3 · round to Fathom
   Otter.ai~partialprobed4/10

   Otter documents an 'Otter API & Webhooks' feature in pricing tiers and a Public API for custom integrations, plus a live MCP server for pulling transcripts/summaries/action items into AI tools, but the runtime probe shows the MCP endpoint is OAuth-gated and both API/MCP access are restricted to Enterprise workspaces (contact account manager), not self-serve; no public OpenAPI/swagger docs were found (all 404). Missing for 10: publicly discoverable API reference docs, evidence of self-serve API key generation for individual/non-enterprise users, and independent confirmation of successful script-based pulls.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

   Fathom exposes a documented REST API with self-serve API-key generation, dedicated endpoints for transcripts and summaries, and webhook payloads that can include transcript/summary/action items, plus official SDKs and a live runtime-verified API surface with OpenAPI spec. Missing for 10: a clearly documented standalone REST 'get action items' endpoint (action items appear only bundled via webhook payloads) and independent (non-vendor) developer corroboration.

   • [claimed-docs] “Head to the API Access section of your User Settings and generate an API key.”
   • [claimed-docs] “All REST API resources are authenticated with API keys generated via the Fathom website's settings area.”
   • [claimed-docs] “If you send `destination_url`, the endpoint will behave in an asynchronous manner. If you do not send `destination_url`, the endpoint will r…”
   • [claimed-docs] “Get summary ... Either the destination URL for where we'll POST the call summary, or the summary for the recording.”
   • [claimed-docs] “Create a webhook to receive new meeting content. At least one of `include_transcript`, `include_crm_matches`, `include_summary`, or `include…”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Fathom
   Otter.ai—none0/10

   No evidence of an llms.txt file or agent-oriented documentation format for Otter.ai; the evidence pack covers MCP server integration and product features but nothing about machine-readable docs for agents to consume directly.

   ⚑ flag

   Fathom✓fullprobed9/10

   Fathom serves a live llms.txt at developers.fathom.ai (HTTP 200, confirmed by probe) that indexes its agent-oriented docs, plus a machine-readable OpenAPI spec and MCP server docs, all directly consumable by an AI agent. missing for 10: no independent/third-party report of an agent successfully consuming llms.txt end-to-end.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.fathom.ai/llms.txt # Fathom API - [Introduction](https://developers.fathom.ai/index.md): Wel…”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”
   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [claimed-docs] “Connect Fathom to any MCP-compatible tool using the server URL below, then authenticate to access your meeting data.”

   proof ↗⚑ flag

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

   weight 2 · round to Fathom
   Otter.ai~partialprobed4/10

   Otter offers a Public API, Webhooks, and an MCP server that could be scripted/integrated into automated pipelines (otter-docs-26, otter-docs-40, otter-probe-rt-1), but these are gated to Enterprise workspaces and there's no documentation of a CLI, SDK, or explicit CI/headless workflow support — the API/MCP surface is aimed at chat-tool integration rather than programmatic batch automation. Missing for 10: documented CLI or SDK for scripted/CI use, explicit CI/automation guides, evidence of non-Enterprise API access, and confirmation the API supports full headless operation (uploading, processing, retrieving) without interactive UI.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

   Fathom exposes a documented, live REST API with API-key auth, SDKs, webhooks, and an OpenAPI spec, all of which can be scripted headlessly in CI to pull meeting/transcript/summary data. However, there's no evidence of a CLI tool, official CI/CD templates, or GitHub Actions integration, and Fathom's core value (meeting capture/bot) is not something CI can trigger — automation is limited to data retrieval/webhooks, not the full product experience. missing for 10: dedicated CLI, CI/CD templates or GitHub Actions examples, evidence of automated meeting-capture triggering from CI, independent (non-vendor) confirmation of headless usage.

   • [claimed-docs] “All REST API resources are authenticated with API keys generated via the Fathom website's settings area.”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff”
   • [claimed-docs] “Create a webhook to receive new meeting content. At least one of `include_transcript`, `include_crm_matches`, `include_summary`, or `include…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Otter.ai—none0/10

   All evidence describes Otter shipping its own MCP *server* so external AI tools (Claude, ChatGPT) can pull Otter's meeting data — this is the reverse of the story, which asks whether a user can plug external MCP servers into Otter so Otter itself can consume their tools. No evidence shows Otter acting as an MCP client consuming third-party MCP servers.

   • [claimed-docs] “ChatGPT, Claude, and other AI chat tools can securely access your meeting knowledge through Otter's MCP Server for deeper analysis and smart…”
   • [claimed-docs] “Connect Otter.ai meeting transcripts and action items to Claude via MCP. Search, recap, and draft follow-ups without leaving the chat.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fathom—none0/10

   All MCP evidence describes Fathom as an MCP *server* that other AI assistants (Claude, ChatGPT) connect to, not Fathom acting as an MCP client that plugs in external MCP servers to use their tools. No evidence shows Fathom's own AI/assistant features consuming external MCP tool servers.

   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [claimed-docs] “Your meeting data, now inside ChatGPT, Claude, and more”
   • [claimed-docs] “Fathom is available as an official connector in Claude”
   • [claimed-docs] “Connect Fathom to any MCP-compatible tool using the server URL below, then authenticate to access your meeting data.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.fathom.ai/mcp returned H…”

   proof ↗⚑ flag

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

   weight 3 · round to Fathom
   Otter.ai✓fullprobed8/10

   Otter documents and ships an official hosted MCP server (mcp.otter.ai) that connects Claude, ChatGPT, and other AI agents to meeting data, with OAuth-based granular permissions, confirmed live via a runtime probe returning a valid OAuth-protected-resource challenge rather than a dead endpoint. Missing for 10: independent third-party (non-vendor) hands-on confirmation of successful agent connection/tool use beyond the auth handshake, and the capability is restricted to Enterprise workspaces rather than universally available.

   • [claimed-docs] “ChatGPT, Claude, and other AI chat tools can securely access your meeting knowledge through Otter's MCP Server for deeper analysis and smart…”
   • [claimed-docs] “Connect Otter.ai meeting transcripts and action items to Claude via MCP. Search, recap, and draft follow-ups without leaving the chat.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [claimed-docs] “Your AI assistant can only access meetings you explicitly authorize”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

   Fathom ships an official hosted MCP server (api.fathom.ai/mcp) documented for connecting AI assistants like Claude and ChatGPT, with official connector status in Claude and CLI setup instructions, and a runtime probe confirms the endpoint is live and speaks MCP OAuth. Missing for 10: independent third-party (non-vendor) hands-on confirmation of the agent connection working end-to-end.

   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [claimed-docs] “Fathom is available as an **official connector** in Claude”
   • [claimed-docs] “Your meeting data, now inside ChatGPT, Claude, and more”
   • [claimed-docs] “claude mcp add fathom -- npx mcp-remote@latest https://api.fathom.ai/mcp”
   • [claimed-docs] “Claude Code supports adding MCP servers directly from the command line.”
   • [claimed-docs] “Connect Fathom to any MCP-compatible tool using the server URL below, then authenticate to access your meeting data.”
   • [probe] “official MCP server documented at https://developers.fathom.ai/mcp-docs/index”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.fathom.ai/mcp returned H…”

   proof ↗⚑ flag

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

   weight 3 · round to Fathom
   Otter.ai~partialprobed4/10

   Otter references a 'Public API' and 'API & Webhooks' as an Enterprise/paid-tier feature (otter-docs-26, otter-docs-40, otter-docs-48), implying programmatic access exists, but no actual API reference, schema, or endpoint documentation is shown, and a live probe found no discoverable OpenAPI/swagger spec (otter-probe-1). The MCP server is real and OAuth-gated (otter-probe-rt-1) but that's a different (agent-tool) interface, not a general-purpose documented public API for driving the product programmatically. missing for 10: published API reference/docs with endpoints and schemas, independent confirmation of working API calls, clarity on which tiers can access it.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

   Fathom publishes a full public REST API with API-key auth, official TypeScript/Python SDKs, webhooks, and a machine-readable OpenAPI 3.1.1 spec, and runtime probes confirm the documented endpoints are live and match the docs exactly. This gives AI-native users a fully documented, verifiable way to drive the product programmatically beyond just MCP/chat connectors. Missing for 10: independent third-party developer reviews/case studies of building against the API.

   • [claimed-docs] “All REST API resources are authenticated with API keys generated via the Fathom website's settings area.”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fathom.ai/openapi.json, https://developers.fathom.ai/swagger.json, https://develo…”

   proof ↗⚑ flag

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

   weight 2 · round to Otter.ai
   Otter.ai~partialprobed7/10

   Otter's MCP server is OAuth-authenticated with granular permissions and explicit meeting-level authorization ('AI assistant can only access meetings you explicitly authorize'), and a runtime probe confirms the endpoint is live and OAuth-gated rather than just a marketing claim. However, this capability is restricted to Enterprise workspaces, and there's no independent evidence of fine-grained scope customization (e.g., read-only vs write, specific resource scoping) beyond vendor description. Missing for 10: independent/hands-on verification of granular scope options, evidence of least-privilege scoping beyond meeting-level authorization, and availability outside Enterprise tier.

   • [claimed-docs] “Your AI assistant can only access meetings you explicitly authorize”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [claimed-docs] “Otter API & Webhooks”

   proof ↗⚑ flag

   Fathom—none0/10

   Fathom's docs describe generating a single account-wide API key in User Settings (fathom-docs-1, fathom-docs-7) and a separate OAuth flow for public apps (fathom-docs-5, fathom-docs-21), but nowhere do the docs describe scopes, roles, or least-privilege permission grants that an AI agent could be issued. The 'users and permissions' endpoint (fathom-docs-9) and admin view-permission controls (fathom-docs-38) govern user-level meeting visibility, not credential scoping for agents. No evidence of restricting an API key/OAuth token to specific resources or actions for agentic use.

   • [claimed-docs] “Head to the API Access section of your User Settings and generate an API key.”
   • [claimed-docs] “All REST API resources are authenticated with API keys generated via the Fathom website's settings area.”
   • [claimed-docs] “Building a **public OAuth app** (for other Fathom users to install)? [Start here](/oauth) instead.”
   • [claimed-docs] “If you're developing a public app that you wish to integrate with Fathom, you should build it using OAuth.”
   • [claimed-docs] “Added users and permissions endpoint.”
   • [claimed-docs] “Admins can access all users' shared meetings by configuring View permissions”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Fathom
   Otter.ai~partialprobed4/10

   Otter documents a Public API, webhooks, and a live, OAuth-gated MCP server (confirmed by runtime probe) that let developers integrate meeting data into custom workflows, which supports 'building against Otter programmatically,' but no evidence names an official SDK (Python/JS/etc.) or provides SDK-style client libraries — only raw API/webhook/MCP endpoints are documented. missing for 10: explicit official SDK documentation/libraries, code samples, language coverage, independent developer corroboration of SDK usage.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

   Fathom documents official TypeScript and Python SDKs that handle auth, pagination, error handling, plus webhook verification helpers, backed by a live REST API and OpenAPI spec confirmed via runtime probes. Missing for 10: independent (non-vendor) developer testimonials or hands-on third-party validation of the SDKs.

   • [claimed-docs] “Use our Typescript or Python SDK.”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff”
   • [claimed-docs] “If you're using our SDK, you can use the verify_webhook helper. Simply call: Fathom.verifyWebhook(webhook_secret, request.headers, request.b…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Fathom
   Otter.ai~partialclaimed5/10

   Otter's pricing page explicitly lists 'Otter API & Webhooks' as a feature on paid plans, confirming webhook subscription capability exists, but there is no documentation describing webhook event types, payload schemas, subscription setup, or independent confirmation of usage. missing for 10: webhook event catalog/documentation, setup/configuration guide, and hands-on or independent verification of webhook delivery.

   • [claimed-docs] “Otter API & Webhooks”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

   Fathom offers documented webhook subscription for meeting events (create-a-webhook API, configurable payload fields like transcript/summary/action items/CRM matches), with signature-based verification via headers and an SDK helper (verify_webhook), all corroborated by docs and consistent with the live API surface. missing for 10: no independent third-party hands-on report of webhook delivery reliability beyond first-party docs.

   • [claimed-docs] “Set up a webhook for your meetings.”
   • [claimed-docs] “Webhooks will send your meeting data (optionally including the summary, transcript, and action items) to a URL of your choice.”
   • [claimed-docs] “Create a webhook to receive new meeting content. At least one of `include_transcript`, `include_crm_matches`, `include_summary`, or `include…”
   • [claimed-docs] “Each webhook request sent from Fathom includes a signature in the request headers, which you can use to confirm the authenticity of the payl…”
   • [claimed-docs] “you can use the `verify_webhook` helper”
   • [claimed-docs] “If you're using our SDK, you can use the verify_webhook helper. Simply call: Fathom.verifyWebhook(webhook_secret, request.headers, request.b…”
   • [claimed-docs] “Webhook verification helps ensure that incoming requests to your endpoint are from Fathom and haven't been altered.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Otter.ai✓fullprobed8/10

   Otter's AI Chat and meeting summaries generate insights, decisions, action items, sentiment, and follow-ups directly from meeting data (otter-docs-1,3,21,37,34,13), and this is corroborated by a live, OAuth-gated MCP endpoint confirmed via runtime probe (otter-probe-rt-1). missing for 10: independent hands-on validation of insight quality/accuracy (community evidence focuses on privacy/recording concerns, not insight usefulness), and MCP/insight features are Enterprise-gated rather than universally available.

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”
   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [claimed-docs] “Analyze patterns and themes across multiple meetings”
   • [claimed-docs] “Monitor sentiment, engagement, and strategic keywords across customer-facing teams to align messaging and positioning.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”

   proof ↗⚑ flag

   Fathom✓fullprobed8/10

   Fathom generates AI summaries, action items, coaching scorecards, and Deal View insights directly from meeting data (docs-13,14,28,40), and surfaces this data conversationally via an official MCP server connected to ChatGPT/Claude (docs-10,19,35, probe-rt-1), confirmed live at runtime. Missing for 10: independent third-party review of insight quality/accuracy and more detail on how suggestions surface in-app beyond summaries/action items.

   • [claimed-docs] “Deal View summarizing insights”
   • [claimed-docs] “Coaching metrics & AI scorecards”
   • [claimed-docs] “AI generated action items”
   • [claimed-docs] “AI summaries instantly available after your call”
   • [claimed-docs] “Your meeting data, now inside ChatGPT, Claude, and more”
   • [claimed-docs] “Connect Fathom to any MCP-compatible tool using the server URL below, then authenticate to access your meeting data.”
   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.fathom.ai/mcp returned H…”

   proof ↗⚑ flag

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

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed6/10

   Otter supports background automation scoped to meetings: scheduled auto-join notetakers, automatic transcription/summarization, auto-extraction of action items, and automatic syncing of notes/action items to CRMs, Jira, Asana, Zendesk, Airtable, S3, etc. (otter-docs-17,9,10,28,29,31,4,3,26,40). This is real autonomous background behavior but it is templated around meeting workflows rather than a general-purpose automation/agent builder where a user defines arbitrary triggers/conditions. Missing for 10: evidence of a flexible, user-configurable automation/workflow engine (beyond Zapier/webhooks) and independent confirmation that these automations reliably run unattended without manual re-triggering.

   • [claimed-docs] “Schedule your AI Meeting Notetaker to automatically join all your Zoom, Microsoft Teams, and Google Meet meetings.”
   • [claimed-docs] “Automatically turn meeting takeaways into support tickets or updates in tools like Zendesk and ServiceNow.”
   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Otter automatically sends transcripts, summaries, and meeting metadata to Airtable.”
   • [claimed-docs] “Export transcripts, summaries, and metadata directly to your Amazon S3 bucket.”
   • [claimed-docs] “Send meeting summaries and action items from Otter to ClickUp to manage everything in one place.”
   • [claimed-docs] “Key deal details, notes, and next steps automatically extracted from every meeting and synced to your CRM.”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fathom~partialprobed5/10

   Fathom offers webhooks, an API/SDK, and an MCP server that let developers build automations reacting to meeting events, which supports background/autonomous workflows, but Fathom itself does not ship a native no-code 'automations' builder or scheduled/autonomous agent runner — users must write their own integration code or use third-party tools (e.g. Zapier) to achieve full autonomy. missing for 10: a first-party no-code automation/workflow builder, evidence of autonomous scheduled or trigger-based agent tasks running natively within Fathom, and independent confirmation of end-to-end automation use in production.

   • [claimed-docs] “Set up a webhook for your meetings.”
   • [claimed-docs] “Webhooks will send your meeting data (optionally including the summary, transcript, and action items) to a URL of your choice.”
   • [claimed-docs] “Create a webhook to receive new meeting content. At least one of `include_transcript`, `include_crm_matches`, `include_summary`, or `include…”
   • [claimed-docs] “Each webhook request sent from Fathom includes a signature in the request headers, which you can use to confirm the authenticity of the payl…”
   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.fathom.ai/mcp returned H…”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”

   proof ↗⚑ flag

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

   weight 3 · round to Otter.ai
   Otter.ai~partialclaimed6/10

   Otter ships a built-in 'Otter AI Chat' assistant that can search meetings, answer questions, draft follow-ups/reports, and auto-extract action items/summaries, which is genuine in-product task delegation (otter-docs-1,3,21,41). However this delegation is scoped narrowly to meeting-related tasks (not general-purpose), and there's no independent/hands-on evidence validating the AI Chat's actual task-completion quality — community evidence only covers transcription accuracy and privacy issues, not the assistant's agentic performance. Missing for 10: independent hands-on validation of Otter AI Chat's task delegation, broader (non-meeting) task scope, and confirmation the chat assistant reliably executes multi-step actions vs. just answering queries.

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”
   • [claimed-docs] “Instantly auto-generate follow-up emails and next steps for client calls, internal reviews, and more.”
   • [claimed-docs] “Stay on track by automatically turning your meeting notes into simple action items with deadlines.”

   proof ↗⚑ flag

   Fathom~partialclaimed3/10

   Fathom's pricing page lists a 'Conversational meeting assistant' feature alongside AI summaries and AI-generated action items, suggesting some built-in AI assistant capability, but there is no documentation of what tasks can be delegated to it, how it's invoked, or its scope of autonomy. Most other AI-native evidence (MCP server, API) describes external assistants pulling Fathom's data rather than a built-in assistant acting on the user's behalf inside the product. Missing for 10: detailed docs on the conversational assistant's task-delegation capabilities, examples of it performing actions, and independent/hands-on confirmation.

   • [claimed-docs] “Conversational meeting assistant”
   • [claimed-docs] “AI generated action items”
   • [claimed-docs] “AI summaries instantly available after your call”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Otter.ai~partialprobed6/10

   Otter AI Chat lets users query meetings, CRMs, and connected apps using natural language to get answers, drafts, and reports (otter-docs-1, otter-docs-11), and this NL interface also works through MCP-connected assistants like Claude/ChatGPT (otter-docs-16, otter-docs-46), confirmed live by a runtime probe. However, evidence is limited to search/chat-style querying rather than broader NL-driven control of the product (e.g., scheduling, settings, workflow actions), and there is no independent hands-on report validating chat accuracy or command breadth. Missing for 10: independent verification of NL Chat's reliability/accuracy, evidence of NL controlling actions beyond querying/summarizing (e.g., configuring integrations, managing recordings via command), and broader command scope beyond meeting Q&A.

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Find key insights from past calls, documents, and more using natural-language.”
   • [claimed-docs] “Connect Otter.ai meeting transcripts and action items to Claude via MCP. Search, recap, and draft follow-ups without leaving the chat.”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

   Fathom ships an official MCP server and official connectors for Claude/ChatGPT, letting users query and interact with meeting data via natural-language prompts in those assistants, and lists a 'Conversational meeting assistant' as a product feature — both are corroborated by live runtime probes of the MCP endpoint. Missing for 10: evidence of a native in-app natural-language command interface (e.g., voice/text commands to control Fathom itself rather than just query data through third-party assistants), and independent user reports of successful conversational task execution beyond data retrieval.

   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [claimed-docs] “Your meeting data, now inside ChatGPT, Claude, and more”
   • [claimed-docs] “Conversational meeting assistant”
   • [claimed-docs] “Fathom is available as an official connector in Claude”
   • [claimed-docs] “Connect Fathom to any MCP-compatible tool using the server URL below, then authenticate to access your meeting data.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.fathom.ai/mcp returned H…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Fathom
   Otter.ai—none0/10

   Otter has a Public API/webhooks and MCP server, so an interactive API reference is a fair ask, but the evidence pack shows no interactive docs or runnable examples — a direct probe for OpenAPI/Swagger specs returned 404s and no docs page with a live API explorer is cited.

   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fathom~partialprobed5/10

   Fathom publishes a full API reference with per-endpoint docs (get-transcript, get-summary, create-a-webhook) and a machine-readable OpenAPI 3.1.1 spec confirmed live at runtime, plus SDKs that simplify calling those endpoints — this gives structured, machine-consumable reference material an AI-native user could explore. However, there's no evidence of an interactive 'try-it-now' console or embedded runnable code examples in the docs themselves (the openapi.json/swagger.json UI paths probed 404, suggesting no rendered interactive explorer). Missing for 10: an in-browser interactive API playground/try-it-now widget, evidence of executable/runnable code snippets directly in docs, and independent confirmation of this interactive experience.

   • [claimed-docs] “If you send `destination_url`, the endpoint will behave in an asynchronous manner. If you do not send `destination_url`, the endpoint will r…”
   • [claimed-docs] “Get summary ... Either the destination URL for where we'll POST the call summary, or the summary for the recording.”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.fathom.ai/openapi.json, https://developers.fathom.ai/swagger.json, https://develo…”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”

   proof ↗⚑ flag

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

   weight 2 · round to Fathom
   Otter.ai—none0/10

   Otter advertises a 'Public API' and webhooks (otter-docs-26, otter-docs-40, otter-docs-48), but a direct probe for machine-readable spec files (openapi.json, swagger.json, etc.) returned 404 on all candidate paths, and no documentation link to an OpenAPI/Swagger spec appears anywhere in the evidence pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fathom✓fullprobed8/10

   Fathom publishes a machine-readable OpenAPI 3.1.1 spec at developers.fathom.ai/api-reference/openapi.yaml, confirmed by a runtime fetch, and this URL is advertised in the site's own llms.txt. Missing for 10: discoverability at conventional paths (openapi.json/swagger.json all 404) and independent third-party corroboration beyond the vendor's own runtime probe.

   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.fathom.ai/llms.txt # Fathom API - [Introduction](https://developers.fathom.ai/index.md): Wel…”
   • [claimed-docs] “All REST API resources are authenticated with API keys generated via the Fathom website's settings area.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Otter.ai—none0/10

   There is evidence of an Otter public API and an MCP server, but no documentation of API versioning scheme or a formal deprecation policy anywhere in the pack; the openapi probe returned 404s. Missing for 10: versioning scheme documentation, changelog/deprecation policy, migration guides, evidence of stable version lifecycle.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fathom—none0/10

   Fathom publishes an OpenAPI spec (versioned 1.0.0) and a changelog tracking added endpoints, but there is no evidence of a documented API versioning scheme or a deprecation policy for breaking changes.

   • [claimed-docs] “Added download recording endpoint.”
   • [claimed-docs] “Added users and permissions endpoint.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Otter.ai~partialclaimed4/10

   Otter offers API/webhooks, unlimited file import, and cross-meeting search/analysis (e.g., 'analyze patterns and themes across multiple meetings', 'search meeting transcripts across all time periods') that could support automation across many meetings at once, but there is no explicit documentation of a bulk-edit/bulk-delete/bulk-tag operation or batch endpoint for acting on many items simultaneously. Missing for 10: documented bulk edit/delete/tag UI or API endpoints, evidence of batch processing limits/behavior, and independent confirmation that cross-meeting operations scale reliably.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Analyze patterns and themes across multiple meetings”
   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Import and transcribe unlimited audio or video files”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fathom~partialprobed4/10

   Fathom's API supports listing meetings, retrieving transcripts/summaries, and webhooks, which could be scripted to iterate across many meetings, but there is no documented bulk/batch endpoint, no pagination-across-thousands example, and no explicit bulk-operations feature (e.g., bulk export, bulk delete, bulk tagging) called out anywhere. missing for 10: dedicated bulk/batch API endpoints, documented pagination for large-scale iteration, bulk write/update operations, and any hands-on evidence of performing bulk actions across many items.

   • [claimed-docs] “List the 10 most recent meetings recorded by you or shared to your team.”
   • [claimed-docs] “Head to the API Access section of your User Settings and generate an API key... List the 10 most recent meetings recorded by you or shared t…”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Otter.ai~partialclaimed5/10

   Otter offers built-in automatic actions (auto-capture of action items, auto-sync to CRM/Zendesk/JIRA/Asana) and lists 'Otter API & Webhooks' and Zapier integration in its pricing page, which would let users build custom event-triggered automations. However, these are fixed, vendor-defined automatic behaviors rather than a documented native interface where users define their own conditional rules; the webhook/Zapier capability is only mentioned as a bullet with no documentation of rule configuration. Missing for 10: a documented rule/automation builder or webhook event catalog showing user-defined trigger-condition-action logic, and independent evidence it works as described.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Salesforce\*, HubSpot\*, Zapier integrations”
   • [claimed-docs] “Automatically turn meeting takeaways into support tickets or updates in tools like Zendesk and ServiceNow.”
   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Stay on track by automatically turning your meeting notes into simple action items with deadlines.”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

   Fathom supports event-driven automation via webhooks (triggered on new meeting content, with signature verification) and topic monitoring alerts, which act as reactive triggers, but there is no evidence of a user-facing rules engine where AI-native users can define arbitrary conditional logic ('if X then do Y') beyond webhook subscriptions to fixed meeting events. missing for 10: a configurable rules/conditions engine, support for custom trigger logic beyond meeting-completion events, and evidence of chained multi-step automated actions.

   • [claimed-docs] “Set up a webhook for your meetings.”
   • [claimed-docs] “Webhooks will send your meeting data (optionally including the summary, transcript, and action items) to a URL of your choice.”
   • [claimed-docs] “Create a webhook to receive new meeting content. At least one of `include_transcript`, `include_crm_matches`, `include_summary`, or `include…”
   • [claimed-docs] “Each webhook request sent from Fathom includes a signature in the request headers, which you can use to confirm the authenticity of the payl…”
   • [claimed-docs] “Automatically monitor key topics so you never miss critical moments”
   • [claimed-docs] “CRM field sync, updating records after meetings automatically”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed4/10

   Otter documents scheduling only in the narrow sense of automatically joining recurring calendar meetings ('Schedule your AI Meeting Notetaker to automatically join all your Zoom, Teams, and Google Meet meetings'), plus webhooks/API/Zapier integrations that could be chained into workflows. There is no evidence of a general recurring-job/workflow scheduler (e.g., scheduled reports, cron-like automation, or repeatable AI-agent tasks beyond meeting attendance). Missing for 10: documented recurring workflow/job scheduling beyond meeting attendance, evidence of cron-like or repeatable automation configuration, independent confirmation of this capability in use.

   • [claimed-docs] “Schedule your AI Meeting Notetaker to automatically join all your Zoom, Microsoft Teams, and Google Meet meetings.”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”

   proof ↗⚑ flag

   Fathom—none0/10

   Fathom is a meeting-notes/transcription product with an API, webhooks, and MCP connector, but nothing in the evidence describes scheduling recurring jobs or automated workflow runs (e.g., cron-like triggers, recurring exports, or repeated automation tasks). Webhooks are event-driven (post-meeting), not scheduled/recurring job execution.

   • [claimed-docs] “Webhooks will send your meeting data (optionally including the summary, transcript, and action items) to a URL of your choice.”
   • [claimed-docs] “Create a webhook to receive new meeting content. At least one of `include_transcript`, `include_crm_matches`, `include_summary`, or `include…”
   • [claimed-docs] “Set up a webhook for your meetings.”

   proof ↗⚑ flag

Calendar

1. product managerI connect Google or Outlook calendar once and control per-meeting-type rules for which meetings get captured automatically

   weight 3 · round drawn
   Otter.ai—none0/10

   Evidence shows Otter can auto-join Zoom/Teams/Google Meet meetings via scheduling (otter-docs-17), but nothing in the pack describes connecting a Google or Outlook calendar or setting per-meeting-type rules for which meetings get captured. This specific calendar-integration and rule-based control capability is unevidenced.

   • [claimed-docs] “Schedule your AI Meeting Notetaker to automatically join all your Zoom, Microsoft Teams, and Google Meet meetings.”

   proof ↗⚑ flag

   Fathom—none0/10

   The evidence pack contains no mention of connecting a Google/Outlook calendar or configuring per-meeting-type auto-capture rules; it only covers API/webhook/SDK/MCP integration and pricing tiers (bot vs bot-free capture, custom bot) with no calendar-workflow specifics.

   ⚑ flag

2. founderI walk into each meeting prepped — the tool surfaces past meetings with the same people and a brief of open threads before the call

   weight 1 · round to Otter.ai
   Otter.ai~partialclaimed4/10

   Otter clearly supports search across past meetings, grouping by team/project/topic, and AI Chat that can surface insights and follow-ups (otter-docs-1, otter-docs-5, otter-docs-11, otter-docs-12, otter-docs-18), which could be used to find prior context with the same people. However, there is no evidence of a proactive, calendar-triggered 'pre-meeting brief' that automatically surfaces past meetings with the same attendees before a call starts — all capabilities described are pull-based search/chat rather than an automated prep experience tied to the upcoming meeting. Missing for 10: automatic calendar-based attendee matching, a dedicated 'pre-call brief' UI/feature, and any independent evidence confirming this specific prep workflow works as described.

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Meetings grouped by team, project, or topic so everyone can find recordings and collaborate in one shared space.”
   • [claimed-docs] “Find key insights from past calls, documents, and more using natural-language.”
   • [claimed-docs] “Keep meetings and notes organized by client, opportunity, or topic to easily revisit key highlights and follow-ups.”
   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Analyze patterns and themes across multiple meetings”

   proof ↗⚑ flag

   Fathom—none0/10

   The evidence covers recording, transcription, summaries, search across calls, CRM sync, and MCP/API access, but nothing documents a proactive pre-meeting brief that surfaces past meetings with the same attendees or open threads ahead of a call — that specific calendar-workflow prep feature is absent from the pack.

   ⚑ flag

Capture

1. product managerThe notetaker reliably captures Zoom, Google Meet, and Microsoft Teams meetings, with recording where I want it

   weight 2 · round to Fathom
   Otter.ai!disputedcontradicted5/10

   Otter documents solid capture breadth: scheduled bot-based joining across Zoom/Teams/Meet (otter-docs-17), plus bot-free desktop and Meet capture for users who don't want a bot present (otter-docs-2, otter-docs-15, otter-docs-38). But hands-on/community reports concretely contradict the 'recording where I want it' promise — users found the bot joining confidential calls unexpectedly, being unable to identify who invited it, and the bot rejoining despite attempts to remove it (otter-comm-8, otter-comm-6, otter-comm-7, otter-comm-5), undermining reliable, controlled capture. missing for 10: independent verification of accurate/controllable scheduling behavior, resolution of the 'can't stop the bot' complaints, and confirmation that bot-free recording is equally reliable across all three platforms.

   • [claimed-docs] “Schedule your AI Meeting Notetaker to automatically join all your Zoom, Microsoft Teams, and Google Meet meetings.”
   • [claimed-docs] “Record conversations directly from your Mac or Windows desktop, without bots joining the call.”
   • [claimed-docs] “Capture impromptu Google Meet calls without a bot present, or transcribe any media from every website.”
   • [claimed-docs] “Record bot-free and manage meetings directly through the Otter desktop app, providing added convenience and flexibility to capture conversat…”
   • [community] “I remember being on sensitive zoom calls and seeing Otter.ai join. Had to track down which person was using it, and even they were clueless …”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”
   • [community] “A lawyer used Otter to record and transcribe a confidential meeting about a child custody case; participants' first awareness of the recordi…”
   • [community] “An AI researcher said Otter recorded a Zoom meeting with investors, then shared a transcription including 'intimate, confidential details' a…”

   proof ↗⚑ flag

   Fathom~partialclaimed4/10

   Evidence confirms Fathom offers flexible recording capture options (bot-based or bot-free/beta) and a 'custom meeting bot' tier, addressing the 'recording where I want it' part of the story, but the evidence pack never explicitly names Zoom, Google Meet, or Microsoft Teams as supported platforms. Missing for 10: explicit platform-by-platform support confirmation for Zoom/Meet/Teams, reliability/uptime evidence, and independent hands-on corroboration of capture across all three platforms.

   • [claimed-docs] “Choice of bot-free (in beta) or bot capture”
   • [claimed-docs] “Capture notes your way – bot or no bot – so you can stay focused on the meeting”
   • [claimed-docs] “Custom meeting bot”

   proof ↗⚑ flag

2. founderCapture and transcribe meetings without a visible bot joining the call — audio is captured from my device so external participants see nothing extra

   weight 3 · round to Otter.ai
   Otter.ai~partialclaimed6/10

   Otter explicitly documents desktop-based, bot-free recording/transcription ("Record conversations directly from your Mac or Windows desktop, without bots joining the call" and "Capture impromptu Google Meet calls without a bot present"), directly matching the story. However, all supporting evidence is vendor-authored; community discussion in the pack focuses entirely on the bot-based joining experience (visible bot, default sharing, privacy issues) rather than validating the bot-free desktop-capture mode, so there is no independent hands-on confirmation this mode works as claimed. Missing for 10: independent/third-party confirmation that bot-free desktop capture actually works and is undetectable to other participants, and detail on what info (if any) is disclosed to other call participants in this mode.

   • [claimed-docs] “Record conversations directly from your Mac or Windows desktop, without bots joining the call.”
   • [claimed-docs] “Capture impromptu Google Meet calls without a bot present, or transcribe any media from every website.”
   • [claimed-docs] “Record bot-free and manage meetings directly through the Otter desktop app, providing added convenience and flexibility to capture conversat…”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

   Fathom's pricing page explicitly advertises a 'bot-free (in beta)' capture option alongside bot capture, and homepage marketing states "Capture notes your way – bot or no bot – so you can stay focused on the meeting," indicating device-based audio capture without a visible bot joining the call. However, this is labeled beta with no technical documentation on how bot-free capture works, no confirmation it captures external participants' audio without their knowledge, and no independent/hands-on corroboration of the feature working as described. Missing for 10: technical docs on bot-free capture mechanism, confirmation of transcription quality/reliability in bot-free mode, independent user reports validating the beta feature works as claimed.

   • [claimed-docs] “Choice of bot-free (in beta) or bot capture”
   • [claimed-docs] “Capture notes your way – bot or no bot – so you can stay focused on the meeting”

   proof ↗⚑ flag

3. founderRecord and transcribe in-person conversations from a mobile app, and those notes land in the same searchable workspace

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed4/10

   Otter's docs confirm bot-free recording from desktop and searchable, shared workspaces (otter-docs-2, otter-docs-5, otter-docs-18, otter-docs-38), and general live transcription/speaker recognition (otter-docs-22), but none of the evidence explicitly describes a mobile app for recording in-person conversations — only desktop capture is documented. Missing for 10: explicit mobile-app in-person recording capability, confirmation that mobile-captured notes sync into the same workspace as other recordings, and independent hands-on evidence of mobile recording quality.

   • [claimed-docs] “Record conversations directly from your Mac or Windows desktop, without bots joining the call.”
   • [claimed-docs] “Meetings grouped by team, project, or topic so everyone can find recordings and collaborate in one shared space.”
   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Live transcription in multiple languages, and speaker recognition.”
   • [claimed-docs] “Record bot-free and manage meetings directly through the Otter desktop app, providing added convenience and flexibility to capture conversat…”

   proof ↗⚑ flag

   Fathom—none0/10

   Evidence pack describes Fathom as a virtual-meeting recorder (bot or bot-free capture of online calls) with API/webhook/MCP integrations, but nothing mentions a mobile app or capturing in-person, non-virtual conversations.

   • [claimed-docs] “Choice of bot-free (in beta) or bot capture”
   • [claimed-docs] “Capture notes your way – bot or no bot – so you can stay focused on the meeting”
   • [claimed-docs] “Automatically monitor key topics so you never miss critical moments”

   proof ↗⚑ flag

Integrations

1. sales leadMeeting notes and summaries sync automatically onto the right contact and deal records in my CRM (HubSpot, Salesforce, Attio)

   weight 3 · round drawn
   Otter.ai~partialclaimed5/10

   Vendor docs claim CRM integrations that extract deal details, notes, and next steps and sync them to Salesforce and HubSpot (otter-docs-4, otter-docs-8, otter-docs-25, otter-docs-36), which covers two of the three named CRMs, but Attio is never mentioned anywhere in the evidence pack. All support is first-party marketing copy with no independent/hands-on confirmation that notes actually land on the correct contact/deal record versus a generic sync, and the pricing page flags the integration with an asterisk suggesting limitations. Missing for 10: Attio support, independent verification of accurate record-level (contact/deal) matching, and confirmation the sync works outside enterprise/marketing claims.

   • [claimed-docs] “Key deal details, notes, and next steps automatically extracted from every meeting and synced to your CRM.”
   • [claimed-docs] “CRM (Salesforce and Hubspot) and document integrations that allow you to query your CRM directly through Otter AI Chat for more personalized…”
   • [claimed-docs] “Salesforce\*, HubSpot\*, Zapier integrations”
   • [claimed-docs] “CRM (Salesforce and Hubspot) and document integrations that allow you to query your CRM directly through Otter AI Chat for more personalized…”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

   Fathom's pricing page explicitly advertises 'CRM field sync, updating records after meetings automatically' and Deal View summarizing insights, indicating native CRM record sync exists, but the evidence pack gives no detail on which CRMs (HubSpot, Salesforce, Attio explicitly named) are supported, how contact/deal matching works, or setup/configuration steps, and no independent/hands-on confirmation of reliability. missing for 10: named support for HubSpot/Salesforce/Attio specifically, technical documentation of the CRM sync mechanism, and independent verification that notes land on the correct contact/deal records.

   • [claimed-docs] “CRM field sync, updating records after meetings automatically”
   • [claimed-docs] “Deal View summarizing insights”

   proof ↗⚑ flag

2. product managerNotes flow into the tools where work happens — Slack channels, Notion pages, and thousands of apps via Zapier

   weight 2 · round to Otter.ai
   Otter.ai✓fullprobed8/10

   Otter documents direct integrations with Slack-adjacent workflow tools (Notion is not explicitly named, but Zapier, Airtable, ClickUp, Zendesk, ServiceNow, JIRA, Asana, Glean, S3, CRM syncs), plus a public API/webhooks and a live, OAuth-gated MCP server confirmed by runtime probe, enabling notes/action items to flow into thousands of apps via Zapier and beyond. Missing for 10: explicit first-party mention of Slack and Notion integrations by name, and independent (non-vendor) confirmation of the Zapier/Airtable/ClickUp integrations actually working in practice.

   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Salesforce\*, HubSpot\*, Zapier integrations”
   • [claimed-docs] “Otter automatically sends transcripts, summaries, and meeting metadata to Airtable.”
   • [claimed-docs] “Send meeting summaries and action items from Otter to ClickUp to manage everything in one place.”
   • [claimed-docs] “Search Otter transcripts, notes, and action items alongside the rest of your company knowledge in Glean.”
   • [claimed-docs] “Automatically turn meeting takeaways into support tickets or updates in tools like Zendesk and ServiceNow.”
   • [claimed-docs] “Otter API & Webhooks”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fathom—none0/10

   The evidence pack shows generic developer infrastructure (REST API, webhooks, SDKs, MCP server for AI assistants) but contains no mention of native Slack, Notion, or Zapier integrations, nor a listed Zapier app — the specific 'thousands of apps' claim in the story has no supporting citation.

   ⚑ flag

Memory

1. product managerAsk questions in natural language across my whole meeting history ("what did we decide about pricing?") and get answers with sources

   weight 2 · round to Otter.ai
   Otter.ai✓fullprobed8/10

   Otter AI Chat and its enterprise MCP server explicitly support natural-language querying across meeting history ('what did we decide about pricing?'-style questions), searching transcripts across all time periods, analyzing patterns across meetings, and citing/linking back to source meetings via the AI Chat interface. This is corroborated by a live runtime probe confirming the MCP endpoint is real and OAuth-gated, not vaporware. Missing for 10: independent hands-on verification of answer accuracy/quality and explicit confirmation that answers include inline source citations (docs describe search/analysis but don't detail citation format in depth).

   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Find key insights from past calls, documents, and more using natural-language.”
   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Analyze patterns and themes across multiple meetings”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

   Fathom advertises a 'Conversational meeting assistant' and 'search across calls' feature, and its official MCP server explicitly lets you bring 'your meeting data...inside ChatGPT, Claude, and more,' enabling natural-language queries over meeting history via a connected AI assistant. However, there's no first-party documentation describing how the built-in conversational assistant answers questions with cited sources, nor detail on cross-meeting recall depth or accuracy. Missing for 10: documented answer format/sourcing for the conversational assistant, evidence of true whole-history semantic search (vs. per-meeting), and independent/hands-on verification of source-accurate answers.

   • [claimed-docs] “Conversational meeting assistant”
   • [claimed-docs] “Clips, playlists + search across calls”
   • [claimed-docs] “Your meeting data, now inside ChatGPT, Claude, and more”
   • [claimed-docs] “Fathom now offers an official MCP (Model Context Protocol) server, allowing you to connect your Fathom meeting data to AI assistants like Ch…”
   • [claimed-docs] “Connect Fathom to any MCP-compatible tool using the server URL below, then authenticate to access your meeting data.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.fathom.ai/mcp returned H…”

   proof ↗⚑ flag

2. product managerSearch across every past meeting — transcripts, summaries, and notes — and jump to the exact moment something was said

   weight 3 · round to Otter.ai
   Otter.ai✓fullprobed8/10

   Otter directly supports cross-meeting search and jump-to-moment via natural-language search over transcripts, summaries, and notes ('Search your meeting transcripts across all time periods', 'Find key insights from past calls, documents, and more using natural-language', grouping by project/topic), plus AI Chat and MCP server for querying meeting knowledge, corroborated by a live runtime probe confirming the MCP endpoint is real and functioning. Missing for 10: independent hands-on verification of precise timestamp jump-to-moment UX and any third-party review confirming search accuracy/recall across large historical archives.

   • [claimed-docs] “Search your meeting transcripts across all time periods”
   • [claimed-docs] “Find key insights from past calls, documents, and more using natural-language.”
   • [claimed-docs] “Meetings grouped by team, project, or topic so everyone can find recordings and collaborate in one shared space.”
   • [claimed-docs] “Otter AI Chat searches across your meetings and connected apps to instantly answer questions and help you create follow-ups, reports, and co…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

   Fathom advertises 'Clips, playlists + search across calls' and keyword alerts/highlights, plus transcripts/summaries accessible via API, suggesting cross-meeting search exists, but the evidence never shows a concrete product UI for searching all transcripts/notes and jumping to a timestamped moment. missing for 10: a documented search UI/feature description showing full-text search across all past meetings with timestamp jump-to, independent/hands-on confirmation of search accuracy or scope, and detail on whether notes (not just transcripts/summaries) are indexed.

   • [claimed-docs] “Clips, playlists + search across calls”
   • [claimed-docs] “Collaboration using comments, folders, keyword alerts, + more”
   • [claimed-docs] “Automatically monitor key topics so you never miss critical moments”
   • [claimed-docs] “If you send `destination_url`, the endpoint will behave in an asynchronous manner. If you do not send `destination_url`, the endpoint will r…”
   • [claimed-docs] “Get summary ... Either the destination URL for where we'll POST the call summary, or the summary for the recording.”

   proof ↗⚑ flag

Summaries

1. product managerAction items with owners are automatically extracted from the conversation and collected somewhere I can track them

   weight 3 · round drawn
   Otter.ai✓fullprobed8/10

   Otter automatically extracts action items with assigned owners from meetings (otter-docs-3, otter-docs-21, otter-docs-30) and collects them in a trackable, searchable workspace, with the ability to sync/push them to task tools like JIRA, Asana, ClickUp, and CRMs for centralized tracking (otter-docs-10, otter-docs-31, otter-docs-4). This is corroborated by an enterprise blog post and integrations page confirming live functionality, plus a working MCP server for querying meeting action items. Missing for 10: independent hands-on verification specifically of action-item/owner extraction accuracy (community evidence focuses on privacy/security concerns rather than confirming or disputing action-item quality).

   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”
   • [claimed-docs] “Stay on track by automatically turning your meeting notes into simple action items with deadlines.”
   • [claimed-docs] “Help your team move faster by sending actions items from meetings into tools they already use, like JIRA, Asana, and others.”
   • [claimed-docs] “Send meeting summaries and action items from Otter to ClickUp to manage everything in one place.”
   • [claimed-docs] “Key deal details, notes, and next steps automatically extracted from every meeting and synced to your CRM.”
   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   Fathom✓fullprobed8/10

   Fathom automatically generates AI action items (fathom-docs-28) and provides webhooks/API that can include action items in structured data delivered to a destination URL (fathom-docs-22, fathom-docs-45), giving PMs a trackable, centralized feed of action items with meeting context. Core capability is well documented and includes runtime confirmation the API is live; missing for 10: explicit evidence of an in-app dashboard specifically tracking action items by owner over time (e.g., a dedicated action-items view) beyond the webhook/API delivery mechanism.

   • [claimed-docs] “AI generated action items”
   • [claimed-docs] “Webhooks will send your meeting data (optionally including the summary, transcript, and action items) to a URL of your choice.”
   • [claimed-docs] “Create a webhook to receive new meeting content. At least one of `include_transcript`, `include_crm_matches`, `include_summary`, or `include…”
   • [claimed-docs] “If you send `destination_url`, the endpoint will behave in an asynchronous manner. If you do not send `destination_url`, the endpoint will r…”
   • [claimed-docs] “Get summary ... Either the destination URL for where we'll POST the call summary, or the summary for the recording.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”

   proof ↗⚑ flag

2. sales leadShape the notes with custom templates or saved prompts per meeting type (discovery call, 1:1, standup) instead of one generic format

   weight 2 · round to Otter.ai
   Otter.ai~partialclaimed4/10

   Otter claims 'fully customizable, AI-powered meeting summaries' that adapt to meeting purpose and functional role (sales, recruiters, PMs), implying some template-like customization, but there's no documentation of a concrete UI for creating/saving custom templates or prompts per meeting type (discovery call vs 1:1 vs standup) that a sales lead could configure themselves. Missing for 10: explicit template/prompt library or editor, evidence of user-defined per-meeting-type presets, and any hands-on confirmation that summaries can be shaped beyond the automatic role-based defaults.

   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”

   proof ↗⚑ flag

   Fathom—none0/10

   Evidence shows AI summaries, action items, and 'advanced/custom call summaries' as a pricing feature, but nothing describes per-meeting-type custom templates or saved prompts (e.g., discovery call vs 1:1 vs standup) that a sales lead could configure and reuse.

   • [claimed-docs] “AI summaries instantly available after your call”
   • [claimed-docs] “Advanced call summaries, including custom summaries”

   proof ↗⚑ flag

3. sales leadThe tool drafts my follow-up email from the meeting so I can review and send it in a couple of clicks

   weight 1 · round to Otter.ai
   Otter.ai✓fullclaimed8/10

   Otter directly claims automatic follow-up email drafting from meetings (otter-docs-41: 'Instantly auto-generate follow-up emails and next steps for client calls'), plus related CRM sync of key deal details and next steps (otter-docs-4) and role-tailored summaries for sales (otter-docs-37), matching the sales-lead persona. Missing for 10: independent hands-on confirmation of the follow-up email drafting feature specifically (evidence is vendor-sourced only) and clarity on whether it's Enterprise-tier gated like other advanced features.

   • [claimed-docs] “Instantly auto-generate follow-up emails and next steps for client calls, internal reviews, and more.”
   • [claimed-docs] “Key deal details, notes, and next steps automatically extracted from every meeting and synced to your CRM.”
   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Help sales leaders coach and forecast more effectively by revealing blockers, objections, and competitor mentions.”

   proof ↗⚑ flag

   Fathom—none0/10

   Fathom's evidence pack covers AI summaries, action items, CRM sync, and conversational meeting assistant features, but nowhere mentions drafting a follow-up email from a meeting for review-and-send. This is a plausible capability for a meeting-notes tool, but no evidence supports it.

   ⚑ flag

4. product managerI get a structured summary right after each meeting — key points, decisions, and next steps — good enough to share without editing

   weight 3 · round to Fathom
   Otter.ai!disputedcontradicted5/10

   Otter's docs claim every meeting is turned into a structured summary with decisions, action items, and next steps (otter-docs-21, otter-docs-3, otter-docs-37, otter-docs-30), which matches the story. However a hands-on account describes Otter emailing an 'absurd, inaccurate outline' after a real meeting (otter-comm-1), directly contradicting the 'good enough to share without editing' bar, and another user notes it doesn't handle accented English well (otter-comm-9), suggesting summaries often need review. Missing for 10: independent benchmarking of summary accuracy/completeness, and confirmation that decisions/action items are reliably correct without user correction.

   • [claimed-docs] “Otter turns every meeting into a clear summary with decisions, action items, and insights.”
   • [claimed-docs] “Clear next steps are automatically captured and assigned from every meeting.”
   • [claimed-docs] “Otter's fully customizable, AI-powered meeting summaries automatically extract actionable insights based on meeting purpose and for differen…”
   • [claimed-docs] “Stay on track by automatically turning your meeting notes into simple action items with deadlines.”
   • [community] “The Otter bot joined two confidential meetings on my behalf and recorded the whole thing, then emailed every member an absurd, inaccurate "o…”
   • [community] “I use Otter pretty religiously to record all work meetings that I participate in... it doesn't do an amazing job with English in various acc…”

   proof ↗⚑ flag

   Fathom✓fullclaimed7/10

   Fathom's core product delivers AI-generated call summaries and action items immediately after calls (fathom-docs-40, fathom-docs-28, fathom-docs-47), retrievable via the get-summary API endpoint (fathom-docs-27/37), matching the PM's need for a shareable post-meeting summary. Missing for 10: explicit documentation of 'decisions' as a distinct summary field and independent/hands-on evidence of summary quality being 'good enough to share without editing'.

   • [claimed-docs] “AI summaries instantly available after your call”
   • [claimed-docs] “AI generated action items”
   • [claimed-docs] “Advanced call summaries, including custom summaries”
   • [claimed-docs] “Get summary ... Either the destination URL for where we'll POST the call summary, or the summary for the recording.”
   • [claimed-docs] “Either the destination URL for where we'll POST the call summary, or the summary for the recording.”

   proof ↗⚑ flag

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

   weight 2 · round to Fathom
   Otter.ai~partialprobed4/10

   Otter documents a Public API/Webhooks (Pro+ tier) and a hosted MCP server for querying meeting transcripts, summaries and action items (otter-docs-26/40/46, otter-probe-rt-1 confirms the MCP endpoint is live and OAuth-gated), but these are limited to read/query-style meeting-data access and are gated to paid/Enterprise workspaces rather than exposing full UI parity (recording controls, collaborative editing, CRM/ticket integrations, admin/security settings) as callable API operations, and no public OpenAPI/reference spec was found (otter-probe-1 all 404). Missing for 10: evidence of API coverage for non-meeting-data UI actions (recording management, collaborative editing, integration configuration), a public API reference/spec, and availability outside Enterprise tier.

   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”
   • [claimed-docs] “Otter's MCP Server connects your meeting data directly to AI tools like Claude and ChatGPT, bringing your meeting intelligence into your eve…”
   • [claimed-docs] “ChatGPT, Claude, and other AI chat tools can securely access your meeting knowledge through Otter's MCP Server for deeper analysis and smart…”
   • [probe] “official MCP server documented at https://otter.ai/blog/otter-for-enterprise-connect-ai-to-ai-with-otters-mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to Otter's hosted MCP server https://mcp.otter.ai/mcp returned HTTP 40…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://otter.ai/openapi.json, https://otter.ai/swagger.json, https://otter.ai/api/openapi.json, htt…”

   proof ↗⚑ flag

   Fathom~partialprobed5/10

   Fathom's REST API/SDKs cover core meeting data (list meetings, transcripts, summaries, recordings, webhooks, users/permissions) confirmed live via runtime probes, so a solid subset of UI functionality is API-accessible. However, many UI/pricing-page features—CRM field sync, Deal View, coaching metrics/scorecards, playlists, comments/folders/keyword alerts, custom bot configuration, SSO/SCIM—have no corresponding documented API endpoints in the evidence, so full UI parity is not demonstrated. Missing for 10: API endpoints for CRM sync, Deal View, coaching/scorecards, playlists/collaboration features, and admin SSO/SCIM management.

   • [claimed-docs] “List the 10 most recent meetings recorded by you or shared to your team.”
   • [claimed-docs] “Added download recording endpoint.”
   • [claimed-docs] “Added users and permissions endpoint.”
   • [claimed-docs] “Webhooks will send your meeting data (optionally including the summary, transcript, and action items) to a URL of your choice.”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://api.fathom.ai/external/v1/meetings returned HTTP 401 ca…”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”
   • [claimed-docs] “CRM field sync, updating records after meetings automatically”
   • [claimed-docs] “Deal View summarizing insights”
   • [claimed-docs] “Coaching metrics & AI scorecards”
   • [claimed-docs] “SSO & SCIM provisioning”

   proof ↗⚑ flag

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

   weight 3 · round to Fathom
   Otter.ai~partialclaimed3/10

   Otter offers some data egress via S3 export of transcripts/summaries/metadata and its public API/webhooks, which could support portability, but there is no documented comprehensive 'export all your data' or account-deletion/data-portability feature, nor any explicit open-format guarantee (e.g., standard transcript formats, full account export tool). missing for 10: dedicated full-account data export tool, explicit open/standard file formats, documented account deletion/data-takeout process, independent confirmation of successful full export.

   • [claimed-docs] “Export transcripts, summaries, and metadata directly to your Amazon S3 bucket.”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Custom Integrations with Otter's Public API: Otter meeting data connects to any system, including niche CRMs and proprietary platforms, unlo…”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

   Fathom's REST API and SDKs let a user programmatically list all meetings, fetch transcripts/summaries, and download recordings, giving JSON/media exports usable outside the platform (fathom-docs-2, fathom-docs-8, fathom-docs-26, fathom-docs-27, fathom-probe-rt-3). However there is no documented one-click 'export all my data' bulk tool or explicit data-portability/account-deletion guarantee, so a user must build their own export script via the API. Missing for 10: a first-party bulk export/archival feature, explicit data-portability policy, and independent confirmation that full historical data (not just per-meeting calls) can be retrieved and account fully closed out.

   • [claimed-docs] “List the 10 most recent meetings recorded by you or shared to your team.”
   • [claimed-docs] “Added download recording endpoint.”
   • [claimed-docs] “If you send `destination_url`, the endpoint will behave in an asynchronous manner. If you do not send `destination_url`, the endpoint will r…”
   • [claimed-docs] “Get summary ... Either the destination URL for where we'll POST the call summary, or the summary for the recording.”
   • [claimed-docs] “Get started in minutes with our official SDKs. They handle authentication, pagination, error handling, and all the complex stuff so you can …”
   • [probe] “PROBE runtime (recorded 2026-09-05): Fathom publishes a machine-readable OpenAPI 3.1.1 spec ('Fathom External API', versioned 1.0.0) at http…”

   proof ↗⚑ flag

Pricing

1. founderStart free and see exactly what each paid tier costs and adds — no "talk to sales" wall for basic use

   weight 2 · round drawn
   Otter.ai~partialclaimed4/10

   The evidence confirms a public /pricing page listing tier-specific features (e.g., otter-docs-23-27 detail limits like '3 lifetime file imports' and '3 concurrent meetings' presumably tied to a plan), and enterprise-tier features explicitly require contacting an account manager (otter-docs-43), implying lower tiers are self-serve. However, no evidence shows actual dollar prices, a clear free-vs-paid breakdown, or confirmation that all paid-tier costs are shown without a sales contact requirement. Missing for 10: explicit price points per tier, confirmation of a self-serve checkout flow, and independent corroboration that no sales-gate exists for basic paid tiers.

   • [claimed-docs] “3 lifetime audio/video file imports”
   • [claimed-docs] “Team vocabulary & taggable speakers”
   • [claimed-docs] “Salesforce\*, HubSpot\*, Zapier integrations”
   • [claimed-docs] “Otter API & Webhooks”
   • [claimed-docs] “Join 3 concurrent meetings”
   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”

   proof ↗⚑ flag

   Fathom~partialclaimed4/10

   The pricing page evidence lists many tier-specific features (CRM sync, coaching metrics, SSO/SCIM, custom bot, etc.) implying a public pricing/feature comparison exists, but no evidence shows actual dollar amounts, a free tier definition, or confirmation that basic use avoids a 'talk to sales' gate for enterprise features like SSO/SCIM. Missing for 10: explicit price figures per tier, confirmation of a self-serve free plan, and absence of a sales-contact requirement for advanced tiers.

   • [claimed-docs] “CRM field sync, updating records after meetings automatically”
   • [claimed-docs] “Deal View summarizing insights”
   • [claimed-docs] “Coaching metrics & AI scorecards”
   • [claimed-docs] “Custom meeting bot”
   • [claimed-docs] “SSO & SCIM provisioning”

   proof ↗⚑ flag

Privacy

1. it adminThe product ships real consent features — participant notifications, in-meeting disclosure, or admin-enforced transparency — not just a policy PDF

   weight 3 · round drawn
   Otter.ai—none0/10

   No evidence pack item describes any real consent mechanism (participant notification banners, in-meeting disclosure indicators, or admin-enforced consent settings); the docs focus entirely on recording, transcription, and integrations. Community reports go further, describing the bot silently joining sensitive/confidential meetings, transcripts shared with all participants by default without prior notice, and company support dismissing responsibility when participants weren't informed — confirming the absence of a genuine consent feature rather than just a documentation gap.

   • [community] “I just deleted my account because of that, also they share conversations with everyone in the meeting by DEFAULT, it wasn't nice receiving a…”
   • [community] “I stopped using them when I saw they share with everyone by default. I wanted the notes only for myself so I could be more present in meetin…”
   • [community] “A lawyer used Otter to record and transcribe a confidential meeting about a child custody case; participants' first awareness of the recordi…”
   • [community] “I remember being on sensitive zoom calls and seeing Otter.ai join. Had to track down which person was using it, and even they were clueless …”
   • [community] “An AI researcher said Otter recorded a Zoom meeting with investors, then shared a transcription including 'intimate, confidential details' a…”

   proof ↗⚑ flag

   Fathom—none0/10

   The evidence pack covers API/SDK/webhook/MCP integration and pricing tiers (bot vs bot-free capture, SSO/SCIM) but contains no mention of participant consent notifications, in-meeting recording disclosure banners, or admin-enforced transparency controls — the core capabilities this story asks about. As a meeting-recording product, this axis clearly applies, but no evidence shows it being delivered.

   ⚑ flag

2. it adminThe vendor documents whether meeting data trains AI models and gives my org an enforceable opt-out, alongside SOC 2 / HIPAA posture

   weight 2 · round to Otter.ai
   Otter.ai~partialcommunity4/10

   Otter documents an enterprise-tier opt-out from AI model training ('Keep your organization's data out of AI model training. Contact your account manager to get started' — otter-docs-43), and community evidence confirms that by default Otter's privacy policy allows using 'anonymized' recordings for training (otter-comm-6), consistent with an opt-in-by-default posture that requires manual admin action to disable. However, the opt-out is not a self-service, enforceable admin toggle — it requires contacting an account manager — and no evidence pack item documents SOC 2 or HIPAA compliance status. Missing for 10: explicit SOC 2/HIPAA certification documentation, a self-service admin-console opt-out control, and independent audit confirmation that opted-out orgs' data is actually excluded from training.

   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”
   • [claimed-docs] “Maintain visibility into account activity with audit trails and logging, supporting your security, compliance, and regulatory reporting need…”
   • [claimed-docs] “Easily control access with secure identity tools like Okta, Azure AD, and others.”

   proof ↗⚑ flag

   Fathom—none0/10

   No evidence in the pack addresses AI training data usage policy, opt-out mechanisms, or SOC 2/HIPAA compliance posture; the docs cover API access, webhooks, SDKs, and MCP integration only. missing for 10: explicit documentation on whether meeting data is used to train AI models, an enforceable opt-out mechanism for orgs, and SOC 2/HIPAA compliance attestations.

   ⚑ flag

3. it adminSet retention policies — auto-delete transcripts and recordings on a schedule — and permanently erase data on demand

   weight 2 · round drawn
   Otter.ai—none0/10

   No evidence describes configurable retention schedules, auto-deletion of transcripts/recordings, or an on-demand data erasure mechanism; enterprise docs mention audit trails and excluding data from AI training but nothing about retention/deletion controls, and community reports even highlight data being retained/shared unexpectedly. This axis clearly applies to an IT-admin/enterprise product but is unaddressed in the evidence.

   • [claimed-docs] “Maintain visibility into account activity with audit trails and logging, supporting your security, compliance, and regulatory reporting need…”
   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”

   proof ↗⚑ flag

   Fathom—none0/10

   No evidence in the pack mentions retention policies, scheduled auto-deletion of transcripts/recordings, or an on-demand data erasure mechanism for admins; evidence only covers API access, webhooks, SDKs, MCP connectors, and pricing tiers.

   ⚑ flag

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

   weight 2 · round drawn
   Otter.ai—none0/10

   No evidence anywhere in the pack mentions data residency, regional storage options, or geographic controls over where data is stored; the closest privacy-related item (otter-docs-43) only addresses excluding data from model training, not storage location. Community evidence discusses data sharing and retention concerns but not regional choice, so this applicable privacy axis has no supporting evidence.

   ⚑ flag

   Fathom—none0/10

   No evidence in the pack mentions data residency, regional storage options, or geographic control over where Fathom stores data; all evidence concerns API/SDK/MCP/webhook functionality and pricing tiers. missing for 10: any mention of region selection, data residency options, or storage location controls.

   ⚑ flag

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

   weight 3 · round to Otter.ai
   Otter.ai~partialcommunity5/10

   Otter explicitly advertises an enterprise-only opt-out ('Keep your organization's data out of AI model training. Contact your account manager to get started' — otter-docs-43), but this is gated behind Enterprise plans and manual account-manager setup rather than a self-serve control available to all users. Community reports (otter-comm-6) note that by default Otter's privacy policy allows use of 'anonymized' recordings as training data, meaning most users cannot avoid this without enterprise contracting. Missing for 10: self-serve toggle for all tiers, independent confirmation the enterprise opt-out is honored in practice, and clarity on what 'anonymized' training use means for non-enterprise accounts.

   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”

   proof ↗⚑ flag

   Fathom—none0/10

   No evidence in the pack addresses AI-training data usage, opt-out settings, or data-privacy policies regarding model training; the evidence is entirely about API/SDK/MCP integration features.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Otter.ai—none0/10

   Otter's docs mention only a narrow enterprise-only opt-out from AI-model training (otter-docs-43) via contacting an account manager, but there is no documented self-service data retention policy, deletion controls, or export/delete workflow for individual users. Community evidence (otter-comm-2, otter-comm-4, otter-comm-6, otter-comm-7) further indicates data is retained in the cloud, used for training unless specially arranged, and that deletion/support requests go unanswered, undermining any claim of user control over retention/deletion.

   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “I just deleted my account because of that, also they share conversations with everyone in the meeting by DEFAULT, it wasn't nice receiving a…”
   • [community] “I have opened a support ticket with screenshots but there is no response, and according to Twitter they are essentially not reviewing ticket…”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”
   • [community] “A lawyer used Otter to record and transcribe a confidential meeting about a child custody case; participants' first awareness of the recordi…”

   proof ↗⚑ flag

   Fathom—none0/10

   The evidence pack covers API access, webhooks, MCP integration, and SDKs, but contains no mention of data retention policies, deletion controls, or user ability to delete recordings/transcripts/data. No documentation of retention settings, data export/purge tools, or deletion endpoints is present.

   ⚑ flag

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

   weight 2 · round drawn
   Otter.ai—none0/10

   No evidence of a telemetry/usage-tracking opt-out setting; the closest item (otter-docs-43) only covers excluding org data from AI model training for Enterprise accounts, not general telemetry/usage analytics opt-out, and community reports actually highlight data-sharing/retention concerns rather than opt-out controls.

   • [claimed-docs] “Keep your organization's data out of AI model training. Contact your account manager to get started.”
   • [community] “A lawyer invited OtterAI to a confidential meeting; the commenter read Otter's privacy statement and found they retain data in the cloud and…”
   • [community] “Otter is the only thing approaching affordable for individuals, but I don't really trust it given they're playing fast and loose with user d…”

   proof ↗⚑ flag

   Fathom—none0/10

   No evidence pack item mentions telemetry, usage tracking, analytics opt-out, or privacy settings of that kind; documentation covers API, webhooks, MCP, and pricing features only.

   ⚑ flag

Sharing

1. sales leadCut a soundbite or highlight clip from a call and share that moment instead of the whole recording

   weight 1 · round to Fathom
   Otter.ai—none0/10

   The evidence pack shows Otter can share full transcripts, notes, and summaries, and sync them to other tools, but there is no mention of cutting a specific soundbite/highlight clip from a recording to share instead of the whole call. Missing for 10: any documented clip/highlight creation or snippet-sharing feature, timestamped audio/video excerpt export, or hands-on evidence of this specific capability.

   • [claimed-docs] “Sync transcriptions and meeting notes for easy editing, sharing, and collaboration with all your teammates.”
   • [claimed-docs] “Keep meetings and notes organized by client, opportunity, or topic to easily revisit key highlights and follow-ups.”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

   Pricing page mentions 'Clips, playlists + search across calls' and 'Playlists of highlights from meetings', indicating Fathom supports creating and sharing highlight clips, but there's no documentation on how clipping/sharing actually works (UI flow, sharing mechanism, permissions). Missing for 10: detailed docs or hands-on evidence of the clip-creation workflow, sharing a clip link vs whole recording, and any independent corroboration.

   • [claimed-docs] “Clips, playlists + search across calls”
   • [claimed-docs] “Playlists of highlights from meetings”

   proof ↗⚑ flag

2. it adminSharing is controlled — private-by-default notes, granular link/folder/workspace permissions, and admin visibility into what's shared

   weight 2 · round to Fathom
   Otter.ai!disputedcontradicted4/10

   Otter documents enterprise access controls (SSO via Okta/Azure AD, audit trails/logging, OAuth-gated granular permissions for MCP) suggesting admin-controlled sharing exists at the enterprise tier, but multiple independent hands-on reports directly contradict the 'private-by-default' premise: users report Otter shares transcripts with every meeting participant by default without consent, and confidential/sensitive meetings were transcribed and distributed without attendees' knowledge, causing real harm (killed business deal, custody case exposure). Missing for 10: documented granular link/folder/workspace-level permission controls, clear evidence of a private-by-default note setting, and resolution of the community reports of default-sharing behavior.

   • [claimed-docs] “Easily control access with secure identity tools like Okta, Azure AD, and others.”
   • [claimed-docs] “Maintain visibility into account activity with audit trails and logging, supporting your security, compliance, and regulatory reporting need…”
   • [claimed-docs] “OAuth-authenticated with granular permissions”
   • [community] “I just deleted my account because of that, also they share conversations with everyone in the meeting by DEFAULT, it wasn't nice receiving a…”
   • [community] “I stopped using them when I saw they share with everyone by default. I wanted the notes only for myself so I could be more present in meetin…”
   • [community] “An AI researcher said Otter recorded a Zoom meeting with investors, then shared a transcription including 'intimate, confidential details' a…”
   • [community] “A lawyer used Otter to record and transcribe a confidential meeting about a child custody case; participants' first awareness of the recordi…”
   • [community] “I remember being on sensitive zoom calls and seeing Otter.ai join. Had to track down which person was using it, and even they were clueless …”

   proof ↗⚑ flag

   Fathom~partialclaimed4/10

   Fathom docs mention admin-configurable view permissions for shared meetings and a dedicated users/permissions API endpoint, plus folders as an organizational feature, suggesting some admin control over sharing. However there's no evidence of private-by-default notes, granular link-level or workspace-level permission settings, or a dedicated admin dashboard for visibility into what's shared. missing for 10: private-by-default note settings, granular link-sharing permissions, workspace-level permission tiers, an admin audit/visibility dashboard for shared content.

   • [claimed-docs] “Admins can access all users' shared meetings by configuring View permissions”
   • [claimed-docs] “Added users and permissions endpoint.”
   • [claimed-docs] “Collaboration using comments, folders, keyword alerts, + more”
   • [claimed-docs] “SSO & SCIM provisioning”

   proof ↗⚑ flag

Transcription

1. founderRun meetings in languages other than English — transcription and summaries support many languages and handle language switching

   weight 2 · round to Otter.ai
   Otter.ai~partialcommunity3/10

   Otter's marketing states 'live transcription in multiple languages' but the evidence pack has no detail on which languages are supported, whether meeting summaries (not just transcripts) are generated in non-English languages, or how mid-meeting language switching is handled. Community evidence only discusses English-accent transcription quality, giving no corroboration of multilingual performance. Missing for 10: documented language list/coverage, evidence that AI summaries (not just live transcript) work in non-English languages, evidence of handling code-switching/mixed-language meetings, and independent hands-on confirmation of non-English accuracy.

   • [claimed-docs] “Live transcription in multiple languages, and speaker recognition.”
   • [community] “I use Otter pretty religiously to record all work meetings that I participate in... it doesn't do an amazing job with English in various acc…”

   proof ↗⚑ flag

   Fathom—none0/10

   The evidence pack contains no mention of multi-language transcription/summary support or language-switching handling anywhere in Fathom's docs, changelog, or pricing pages — all references focus on API access, webhooks, MCP integration, and English-oriented feature descriptions.

   ⚑ flag

2. product managerThe transcript attributes words to the right named speakers (diarization plus real name matching), not just "Speaker 1/2"

   weight 3 · round to Otter.ai
   Otter.ai~partialcommunity4/10

   Otter's docs mention 'speaker recognition' during live transcription and 'taggable speakers' in pricing tiers, suggesting some diarization plus a manual tagging mechanism to assign real names, but there's no detailed documentation of automatic real-name matching accuracy or independent verification of correctness. Community threads only discuss transcription accuracy for accents, not speaker attribution reliability. Missing for 10: documentation of automatic vs. manual name assignment, accuracy benchmarks for speaker identification, and independent hands-on verification that speakers are correctly named rather than generic labels.

   • [claimed-docs] “Live transcription in multiple languages, and speaker recognition.”
   • [claimed-docs] “Team vocabulary & taggable speakers”
   • [community] “I use Otter pretty religiously to record all work meetings that I participate in... it doesn't do an amazing job with English in various acc…”

   proof ↗⚑ flag

   Fathom—none0/10

   No evidence in the pack addresses diarization or speaker-name matching in transcripts; the pack only covers API access, webhooks, MCP integration, and pricing tiers. This is a fair axis for a meeting-transcription product, but nothing here confirms accurate speaker attribution or real-name matching.

   ⚑ flag

3. product managerThe vendor documents how transcription actually works and its quality (models, accuracy claims, known limits) rather than just saying "AI-powered"

   weight 3 · round drawn
   Otter.ai—none0/10

   The evidence pack shows only marketing-style feature claims (AI-powered summaries, live transcription, speaker recognition) with no vendor documentation of the transcription model(s) used, quantified accuracy benchmarks, or explicitly stated known limitations (e.g., accent/language performance, noise handling). Community evidence even flags real accuracy gaps (accents, non-English speech) that the vendor's own docs never acknowledge, reinforcing the absence of transparent quality documentation.

   • [claimed-docs] “Live transcription in multiple languages, and speaker recognition.”
   • [community] “I use Otter pretty religiously to record all work meetings that I participate in... it doesn't do an amazing job with English in various acc…”
   • [community] “I'm generally a 'hater' of the cloud, and I have to admit that Otter is very good. I used it speaking with someone using airpods on a shitty…”

   proof ↗⚑ flag

   Fathom—none0/10

   The evidence pack contains extensive docs on API access, webhooks, MCP integration, and pricing tiers, but nothing about transcription models, accuracy claims, language support, or known limitations of the transcription/AI engine itself — everything is marketed generically as 'AI summaries' or 'AI generated action items' without technical detail.

   ⚑ flag