Fireflies.ai vs Otter.ai

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
   Fireflies.ai~partialprobed4/10

   Fireflies exposes a documented GraphQL API (bearer-token auth) with transcript/action-item queries that a developer or agent could use to push action items into an external tracker, and MCP servers exist for docs/data access, but there is no evidence of native, first-party integrations, webhooks, or automations targeting Linear, Jira, or Asana specifically. missing for 10: documented webhooks, native Linear/Jira/Asana connectors, or automation templates that file action items into a project tracker.

   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “The transcript query is designed to fetch details associated with a specific transcript ID.”
   • [claimed-docs] “The Fireflies API is built on top of GraphQL... This API allows you to retrieve exactly the data you need in a structured format.”
   • [claimed-docs] “We use a standard bearer token authentication mechanism.”
   • [probe] “PROBE runtime (recorded 2026-09-05): a keyless GraphQL query POSTed to the live endpoint https://api.fireflies.ai/graphql returned the docum…”
   • [claimed-docs] “Get detailed notes, action items, and customized summaries instantly after every meeting.”

   proof ↗⚑ flag

   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

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 Fireflies.ai
   Fireflies.ai✓fullprobed8/10

   Fireflies documents and runtime evidence confirm a live, OAuth-gated hosted MCP server (api.fireflies.ai/mcp) that lets AI tools query meeting data with 'no API keys required,' matching the OAuth/no-glue-code requirement, and this is corroborated by a real runtime probe returning the expected OAuth challenge. Missing for 10: explicit documentation naming Claude (only ChatGPT's Deep Research is called out) and explicit confirmation that action-item queries specifically (not just transcripts/search) are exposed via the MCP tool surface rather than only the separate GraphQL API.

   • [claimed-docs] “Once connected, you can query your Fireflies data directly through ChatGPT's Deep Research feature.”
   • [claimed-docs] “Compare the objections mentioned in calls with Enterprise prospects versus SMB prospects this quarter”
   • [claimed-docs] “You can now connect Fireflies to ChatGPT using our OAuth integration—no API keys required.”
   • [probe] “official MCP server documented at https://guide.fireflies.ai/articles/8272956938-learn-about-the-fireflies-mcp-server-model-context-protocol”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP server https://api.fireflies.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   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

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 Fireflies.ai
   Fireflies.ai✓fullprobed8/10

   Fireflies documents a self-serve GraphQL API with bearer-token API keys (generated via Integrations UI), and dedicated queries for transcripts, transcript details, and audio upload, with runtime probes confirming the live endpoint enforces the documented auth scheme. Action items and summaries are surfaced as part of the transcript/meeting data model referenced in docs and marketing copy. missing for 10: no explicit documented query/field example returning action items or AI summary output specifically, and no independent third-party developer report confirming successful end-to-end script usage beyond docs and probes.

   • [claimed-docs] “Navigate to the Integrations section 3. Click on Fireflies API 4. Copy and store your API key securely”
   • [claimed-docs] “We use a standard bearer token authentication mechanism. This means that to make authorized requests to the API, you must include an `Author…”
   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “The transcript query is designed to fetch details associated with a specific transcript ID.”
   • [claimed-docs] “The Fireflies API is built on top of GraphQL... This API allows you to retrieve exactly the data you need in a structured format.”
   • [claimed-docs] “Make your first request in under 5 minutes. This guide provides step-by-step instructions to make your first query with our GraphQL API”
   • [claimed-docs] “The uploadAudio mutation allows you to upload audio files to Fireflies.ai for transcription.”
   • [probe] “PROBE runtime (recorded 2026-09-05): a keyless GraphQL query POSTed to the live endpoint https://api.fireflies.ai/graphql returned the docum…”
   • [claimed-docs] “Get detailed notes, action items, and customized summaries instantly after every meeting.”

   proof ↗⚑ flag

   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

Agent access

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

   weight 2 · round to Fireflies.ai
   Fireflies.ai✓fullprobed9/10

   Fireflies hosts an llms.txt file confirmed live at https://docs.fireflies.ai/llms.txt (HTTP 200) and also runs an agent-oriented docs MCP server that completed a full keyless handshake, letting agents search documentation directly. This gives AI-native users two concrete, verified paths to point an agent at agent-oriented docs. Missing for 10: no independent third-party corroboration of llms.txt usage/adoption beyond the probe.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.fireflies.ai/llms.txt # Fireflies ## Docs - [Introduction](https://docs.fireflies.ai/getting-star…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the Fireflies docs MCP server at https://docs.fireflies.ai/mcp completed a FULL keyless JSON-RPC initia…”
   • [claimed-docs] “The Fireflies Documentation MCP Server enables AI tools to search and retrieve information directly from the Fireflies documentation.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Fireflies.ai
   Fireflies.ai~partialprobed6/10

   Fireflies exposes a documented GraphQL API with bearer-token auth (uploadAudio, transcripts queries) that is confirmed live via runtime probes, enabling headless scripted/automated use outside the UI. However there's no CLI, SDK, or explicit CI/pipeline documentation or examples showing scheduled/unattended automation workflows. missing for 10: official CLI or SDK for automation, documented CI/cron usage patterns, independent evidence of real-world headless deployment.

   • [claimed-docs] “We use a standard bearer token authentication mechanism. This means that to make authorized requests to the API, you must include an `Author…”
   • [claimed-docs] “The `uploadAudio` mutation allows you to upload audio files to Fireflies.ai for transcription.”
   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [probe] “PROBE runtime (recorded 2026-09-05): a keyless GraphQL query POSTed to the live endpoint https://api.fireflies.ai/graphql returned the docum…”
   • [claimed-docs] “Make your first request in under 5 minutes. This guide provides step-by-step instructions to make your first query with our GraphQL API”

   proof ↗⚑ flag

   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

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

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

   All evidence describes Fireflies as an MCP *server* (its docs MCP server and its data MCP server that ChatGPT/other agents connect to), not as a client that lets users plug external MCP servers into Fireflies so it can consume their tools. No documentation shows Fireflies' own AI assistant (Fred) accepting third-party MCP servers as tool sources.

   • [claimed-docs] “The Fireflies Documentation MCP Server enables AI tools to search and retrieve information directly from the Fireflies documentation.”
   • [claimed-docs] “Once connected, you can query your Fireflies data directly through ChatGPT's Deep Research feature.”
   • [probe] “official MCP server documented at https://guide.fireflies.ai/articles/8272956938-learn-about-the-fireflies-mcp-server-model-context-protocol”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP server https://api.fireflies.ai/mcp returned HTTP 40…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the Fireflies docs MCP server at https://docs.fireflies.ai/mcp completed a FULL keyless JSON-RPC initia…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Fireflies.ai
   Fireflies.ai✓fullprobed9/10

   Fireflies ships an official hosted MCP server (api.fireflies.ai/mcp, OAuth-gated) plus a separate docs MCP server, both confirmed live via runtime probes, allowing AI agents like ChatGPT Deep Research to query Fireflies data. missing for 10: independent third-party hands-on write-up beyond vendor docs/probes.

   • [claimed-docs] “The Fireflies Documentation MCP Server enables AI tools to search and retrieve information directly from the Fireflies documentation.”
   • [claimed-docs] “Once connected, you can query your Fireflies data directly through ChatGPT's Deep Research feature.”
   • [claimed-docs] “You can now connect Fireflies to ChatGPT using our OAuth integration—no API keys required.”
   • [probe] “official MCP server documented at https://guide.fireflies.ai/articles/8272956938-learn-about-the-fireflies-mcp-server-model-context-protocol”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP server https://api.fireflies.ai/mcp returned HTTP 40…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the Fireflies docs MCP server at https://docs.fireflies.ai/mcp completed a FULL keyless JSON-RPC initia…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Fireflies.ai
   Fireflies.ai✓fullprobed9/10

   Fireflies documents a full public GraphQL API with bearer-token auth, queries/mutations (transcripts, uploadAudio), and a quickstart guide, and runtime probes confirm the live GraphQL endpoint enforces auth exactly as documented. This is corroborated by hands-on probes, not just vendor claims. Missing for 10: no OpenAPI/swagger spec discoverable and no independent third-party developer testimonial beyond internal docs.

   • [claimed-docs] “We use a standard bearer token authentication mechanism. This means that to make authorized requests to the API, you must include an `Author…”
   • [claimed-docs] “The `uploadAudio` mutation allows you to upload audio files to Fireflies.ai for transcription.”
   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “The Fireflies API is built on top of GraphQL... This API allows you to retrieve exactly the data you need in a structured format.”
   • [claimed-docs] “Make your first request in under 5 minutes. This guide provides step-by-step instructions to make your first query with our GraphQL API”
   • [probe] “PROBE runtime (recorded 2026-09-05): a keyless GraphQL query POSTed to the live endpoint https://api.fireflies.ai/graphql returned the docum…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.fireflies.ai/openapi.json, https://docs.fireflies.ai/swagger.json, https://docs.firefli…”

   proof ↗⚑ flag

   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

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

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

   Fireflies' API uses a single bearer-token API key per account with full account-level access (docs-2, docs-3, docs-23); there is no evidence of scoped, role-limited, or least-privilege credential issuance for agents (e.g., no per-agent scopes, read-only keys, or restricted-permission tokens). The OAuth flow mentioned is for connecting to ChatGPT, not for issuing narrower-scope credentials, and admin controls (Rules Engine, Super Admin) govern meeting access, not API credential scoping.

   • [claimed-docs] “Navigate to the Integrations section 3. Click on Fireflies API 4. Copy and store your API key securely”
   • [claimed-docs] “We use a standard bearer token authentication mechanism. This means that to make authorized requests to the API, you must include an `Author…”
   • [claimed-docs] “We use a standard bearer token authentication mechanism.”
   • [claimed-docs] “You can now connect Fireflies to ChatGPT using our OAuth integration—no API keys required.”
   • [claimed-docs] “Full meeting access to your entire workspace by upgrading to Super Admin status.”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

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

   Evidence shows a GraphQL API with bearer-token auth and MCP servers, but no official language SDKs (e.g., Python/JS client libraries) are documented or referenced anywhere in the pack.

   • [claimed-docs] “The Fireflies API is built on top of GraphQL... This API allows you to retrieve exactly the data you need in a structured format.”
   • [claimed-docs] “We use a standard bearer token authentication mechanism. This means that to make authorized requests to the API, you must include an `Author…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.fireflies.ai/openapi.json, https://docs.fireflies.ai/swagger.json, https://docs.firefli…”

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

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

   The evidence pack covers GraphQL API, MCP servers, and OAuth integration but contains no mention of webhooks or event-based subscriptions anywhere in the docs, pricing, or security pages provided.

   ⚑ flag

   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

Agentic features

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

   weight 2 · round to Otter.ai
   Fireflies.ai✓fullclaimed7/10

   Fireflies generates AI-driven meeting notes, action items, and customized summaries automatically (fireflies-docs-10), plus an AskFred AI assistant for querying meeting data and cross-meeting insights like comparing objections across prospect segments (fireflies-docs-18, fireflies-docs-24). These are in-product AI-generated insights/suggestions surfaced directly to users. missing for 10: independent/hands-on user reviews validating quality of AskFred's insights, and more detail on the breadth/accuracy of automated suggestions beyond marketing copy.

   • [claimed-docs] “Get detailed notes, action items, and customized summaries instantly after every meeting.”
   • [claimed-docs] “AskFred: AI assistant”
   • [claimed-docs] “Compare the objections mentioned in calls with Enterprise prospects versus SMB prospects this quarter”
   • [claimed-docs] “Conversation intelligence Team analytics (for admins)”

   proof ↗⚑ flag

   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

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

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

   Fireflies offers automation-adjacent features (auto-join calendar meetings, rules engine for admin workflows, API/MCP access) but there's no evidence of user-configurable autonomous agentic automations that run in the background beyond meeting recording/transcription triggers. missing for 10: documented workflow/automation builder for arbitrary recurring agentic tasks, evidence of scheduled/triggered actions beyond meeting auto-join, independent confirmation of autonomous multi-step automation execution.

   • [claimed-docs] “Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record, transcribe, and summarize.”
   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Audit Logs ([API](https://docs.fireflies.ai/graphql-api/query/audit-events#audit-events))”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Otter.ai
   Fireflies.ai~partialclaimed4/10

   Fireflies advertises 'AskFred: AI assistant' as a paid feature and an AI bot (fred@fireflies.ai) that can be invited to meetings to record, transcribe, and summarize, which is a built-in assistant a user can delegate meeting-related tasks to. However, evidence never details what tasks AskFred can perform beyond note-taking/summarization, provides no hands-on walkthrough, and gives no independent corroboration of its task-delegation capabilities. Missing for 10: detailed docs on AskFred's task scope/commands, hands-on or independent verification of delegating tasks to it, and clarity on limits beyond meeting summarization.

   • [claimed-docs] “Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record, transcribe, and summarize.”
   • [claimed-docs] “AskFred: AI assistant”
   • [claimed-docs] “Get detailed notes, action items, and customized summaries instantly after every meeting.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Fireflies.ai
   Fireflies.ai✓fullprobed7/10

   Fireflies ships an AskFred AI assistant and an official remote MCP server (OAuth-gated, live per runtime probe) that lets users query meeting data via natural language through ChatGPT/Deep Research, with documented example queries like 'Compare the objections mentioned in calls...'. missing for 10: no independent/hands-on review of NL command accuracy or breadth beyond the vendor's own examples, and no evidence of NL support outside the ChatGPT/MCP integration path.

   • [claimed-docs] “AskFred: AI assistant”
   • [claimed-docs] “Once connected, you can query your Fireflies data directly through ChatGPT's Deep Research feature.”
   • [claimed-docs] “Compare the objections mentioned in calls with Enterprise prospects versus SMB prospects this quarter”
   • [claimed-docs] “You can now connect Fireflies to ChatGPT using our OAuth integration—no API keys required.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP server https://api.fireflies.ai/mcp returned HTTP 40…”
   • [probe] “official MCP server documented at https://guide.fireflies.ai/articles/8272956938-learn-about-the-fireflies-mcp-server-model-context-protocol”

   proof ↗⚑ flag

   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

Api quality

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

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

   Fireflies documents its GraphQL API with markdown reference pages (queries/mutations) and a docs MCP server for AI search, but there is no evidence of an interactive API reference with runnable/try-it examples (e.g., GraphQL playground or Swagger UI); a probe explicitly found no OpenAPI/swagger spec at expected paths.

   • [claimed-docs] “The `uploadAudio` mutation allows you to upload audio files to Fireflies.ai for transcription.”
   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “The Fireflies API is built on top of GraphQL... This API allows you to retrieve exactly the data you need in a structured format.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.fireflies.ai/openapi.json, https://docs.fireflies.ai/swagger.json, https://docs.firefli…”

   proof ↗⚑ flag

   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

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

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

   Fireflies exposes a GraphQL API (not REST/OpenAPI), and an explicit probe for openapi.json/swagger.json at multiple standard paths returned 404s with no alternative machine-readable spec (e.g., GraphQL SDL/introspection download) surfaced in docs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.fireflies.ai/openapi.json, https://docs.fireflies.ai/swagger.json, https://docs.firefli…”
   • [claimed-docs] “The Fireflies API is built on top of GraphQL... This API allows you to retrieve exactly the data you need in a structured format.”

   proof ↗⚑ flag

   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

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

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

   The docs describe a single GraphQL API (queries/mutations) but there is no mention of API versioning, version numbers, changelogs, or a documented deprecation policy anywhere in the evidence pack; no evidence of any versioning scheme or deprecation communication exists.

   ⚑ flag

   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

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

   weight 2 · round drawn
   Fireflies.ai~partialprobed4/10

   The GraphQL API's transcripts query supports fetching filtered lists (e.g., by attendee emails), enabling bulk-read automation, and the MCP server exposes this to AI agents. However, there is no documented batch/bulk mutation (e.g., bulk delete, bulk tag, bulk update) across many items — only single-item mutations like uploadAudio are shown. missing for 10: explicit bulk write/update/delete endpoints, batch mutation support, pagination/rate-limit guidance for large-scale bulk operations, independent confirmation of bulk workflows in practice.

   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “Filter meetings that contain any of these emails as attendees. Accepts an array of email addresses.”
   • [claimed-docs] “The `uploadAudio` mutation allows you to upload audio files to Fireflies.ai for transcription.”
   • [probe] “PROBE runtime (recorded 2026-09-05): a keyless GraphQL query POSTed to the live endpoint https://api.fireflies.ai/graphql returned the docum…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Otter.ai
   Fireflies.ai~partialclaimed4/10

   Fireflies explicitly advertises a 'Rules Engine' with 'Automation workflows for admins to have control over meeting access and privacy,' which is direct evidence of rule-based, event-triggered automation. However, this is scoped narrowly to admin governance (access/privacy controls) rather than a general-purpose, user-defined trigger-action automation system for AI-native workflows, and there's no documented API/webhook mechanism for arbitrary custom rules. Missing for 10: evidence of broader user-configurable triggers/actions beyond admin privacy controls, webhook/event API for custom automations, and independent confirmation of the Rules Engine's flexibility.

   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Full meeting access to your entire workspace by upgrading to Super Admin status.”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

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

   The evidence shows GraphQL API access, MCP servers, and admin 'automation workflows' for meeting access/privacy controls, but nothing about scheduling recurring jobs or workflows (e.g., cron-like triggers, recurring API calls, workflow automation for tasks) that an AI-native user could set up and have run repeatedly.

   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “The Fireflies API is built on top of GraphQL... This API allows you to retrieve exactly the data you need in a structured format.”

   proof ↗⚑ flag

   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

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 to Fireflies.ai
   Fireflies.ai~partialclaimed5/10

   Docs confirm calendar autojoin (Google Meet) and an admin-facing 'Rules Engine' for controlling meeting access/privacy, suggesting some rule-based control over capture, but there is no concrete evidence of a per-meeting-type configuration UI (e.g., rules keyed to meeting title/type) or explicit Outlook calendar connection flow. missing for 10: explicit Google/Outlook calendar-connect walkthrough, granular per-meeting-type capture rule examples, and any hands-on/independent confirmation of this workflow.

   • [claimed-docs] “Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record, transcribe, and summarize.”
   • [claimed-docs] “Automatically record your Google Meet calls and get real-time transcripts.”
   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Full meeting access to your entire workspace by upgrading to Super Admin status.”

   proof ↗⚑ flag

   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

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
   Fireflies.ai—none0/10

   Fireflies documents transcript search/filtering by attendee email and analytics tools, which could technically support building such a feature, but there is no evidence of a native pre-meeting briefing or 'past meetings with same people + open threads' surfacing feature before a call.

   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “Filter meetings that contain any of these emails as attendees. Accepts an array of email addresses.”
   • [claimed-docs] “AskFred: AI assistant”

   proof ↗⚑ flag

   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

Capture

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

   weight 2 · round to Fireflies.ai
   Fireflies.ai~partialcommunity6/10

   Docs confirm the fred@fireflies.ai bot can autojoin calendar meetings and specifically call out automatic Google Meet recording, plus admin-level 'Rules Engine' controls over meeting access/privacy for recording governance, but Zoom and Microsoft Teams are never explicitly named as supported recording targets in the pack, and a community comment questions the platform's overall complexity without concretely refuting capture reliability. missing for 10: explicit Zoom/Teams recording documentation, granular per-meeting recording-location controls, and independent hands-on confirmation of multi-platform capture reliability.

   • [claimed-docs] “Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record, transcribe, and summarize.”
   • [claimed-docs] “Automatically record your Google Meet calls and get real-time transcripts.”
   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [community] “Don't... I've tried and it's incredibly complex... there is another Startup called tldv.io that went even further with their tech than flies…”

   proof ↗⚑ flag

   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

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
   Fireflies.ai—none0/10

   Fireflies' documented capture mechanism is bot-based — 'Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record' — meaning a visible bot participant joins calls; there is no evidence of a desktop-app/device-audio capture mode that avoids a visible bot. The only alternative is uploadAudio for pre-recorded files, which doesn't address live-meeting capture without a bot.

   • [claimed-docs] “Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record, transcribe, and summarize.”
   • [claimed-docs] “The `uploadAudio` mutation allows you to upload audio files to Fireflies.ai for transcription.”

   proof ↗⚑ flag

   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

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
   Fireflies.ai—none0/10

   The evidence pack covers meeting bot recording (autojoin, Google Meet), API uploadAudio, and MCP integrations, but contains no mention of a mobile app for recording in-person conversations or notes syncing to the same workspace from mobile capture.

   ⚑ flag

   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

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 to Otter.ai
   Fireflies.ai—none0/10

   The evidence pack contains detailed docs on the GraphQL API, MCP servers, and general meeting features, but nothing about native HubSpot, Salesforce, or Attio integrations or automatic syncing of notes/summaries to CRM contact/deal records. Without any documented CRM connector or sync workflow, this capability is unevidenced.

   ⚑ flag

   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

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
   Fireflies.ai—none0/10

   The evidence pack covers Fireflies' GraphQL API, MCP servers, and security/admin features, but contains no mention of native Slack, Notion, or Zapier integrations or any 'thousands of apps' automation ecosystem — the specific capability the story asks about is simply absent from the provided evidence.

   ⚑ flag

   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

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
   Fireflies.ai~partialprobed6/10

   Fireflies ships an 'AskFred' AI assistant and an MCP server that lets natural-language tools like ChatGPT Deep Research query meeting data with prompts like 'compare objections in Enterprise vs SMB calls this quarter,' which is direct evidence of cross-meeting natural-language Q&A. However, the evidence never shows answers being returned with explicit sourced excerpts/citations back to specific meetings, and there's no independent hands-on validation of answer quality. Missing for 10: documented citation/sourcing behavior in AskFred/MCP answers, and third-party verification of accuracy across large meeting histories.

   • [claimed-docs] “AskFred: AI assistant”
   • [claimed-docs] “Compare the objections mentioned in calls with Enterprise prospects versus SMB prospects this quarter”
   • [claimed-docs] “Once connected, you can query your Fireflies data directly through ChatGPT's Deep Research feature.”
   • [claimed-docs] “You can now connect Fireflies to ChatGPT using our OAuth integration—no API keys required.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP server https://api.fireflies.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   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

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
   Fireflies.ai~partialprobed6/10

   Fireflies provides cross-meeting search via AskFred AI assistant, the MCP server (which explicitly supports queries like comparing objections across many calls), and GraphQL queries (transcripts/transcript) that can filter by attendees and fetch specific transcript details, plus notes/summaries. However, the evidence never explicitly documents jumping to a precise timestamp/moment within a transcript from search results. Missing for 10: explicit documentation of timestamp-level deep-linking or in-transcript moment navigation from search results, and independent/hands-on confirmation of search accuracy across large meeting histories.

   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “The transcript query is designed to fetch details associated with a specific transcript ID.”
   • [claimed-docs] “AskFred: AI assistant”
   • [claimed-docs] “Compare the objections mentioned in calls with Enterprise prospects versus SMB prospects this quarter”
   • [claimed-docs] “Filter meetings that contain any of these emails as attendees. Accepts an array of email addresses.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP server https://api.fireflies.ai/mcp returned HTTP 40…”

   proof ↗⚑ flag

   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

Summaries

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

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

   Fireflies docs claim it produces 'detailed notes, action items, and customized summaries instantly after every meeting' and offers a Rules Engine/team workflows for admins, which implies action items are captured and accessible via dashboard/API (transcripts query). However, there's no explicit evidence of owner assignment/attribution per action item, a dedicated tracking view/board, or task-management integration (e.g., sync to a task tool) beyond generic summary output. missing for 10: explicit owner-attribution logic, a dedicated action-item tracking dashboard, and third-party corroboration of accuracy/completeness.

   • [claimed-docs] “Get detailed notes, action items, and customized summaries instantly after every meeting.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”

   proof ↗⚑ flag

   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

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
   Fireflies.ai—none0/10

   The evidence pack shows only generic 'customized summaries' language and API/MCP mechanics, but no documentation of configurable templates or saved prompts tied to meeting types (discovery call, 1:1, standup) that a sales lead could select or author.

   • [claimed-docs] “Get detailed notes, action items, and customized summaries instantly after every meeting.”

   proof ↗⚑ flag

   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

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
   Fireflies.ai—none0/10

   Fireflies documents meeting notes, action items, and customized summaries (fireflies-docs-10) plus an AskFred AI assistant (fireflies-docs-18), but no evidence pack item mentions drafting or auto-composing a follow-up email a sales rep can review and send in a couple of clicks. This is a fair capability to expect from a meeting-notes tool, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Get detailed notes, action items, and customized summaries instantly after every meeting.”
   • [claimed-docs] “AskFred: AI assistant”

   proof ↗⚑ flag

   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

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 Fireflies.ai
   Fireflies.ai✓fullclaimed7/10

   Fireflies explicitly markets 'detailed notes, action items, and customized summaries instantly after every meeting' with AI-driven summarization (AskFred) and structured meeting notes, matching the PM story of a ready-to-share post-meeting summary. Missing for 10: no independent/hands-on review confirming summary quality is 'good enough to share without editing', and no detail on how decisions/next-steps are specifically structured in the output beyond marketing copy.

   • [claimed-docs] “Get detailed notes, action items, and customized summaries instantly after every meeting.”
   • [claimed-docs] “AskFred: AI assistant”
   • [claimed-docs] “Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record, transcribe, and summarize.”
   • [claimed-docs] “Real-time notes & live transcriptions”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Fireflies.ai
   Fireflies.ai~partialprobed6/10

   Fireflies offers a documented GraphQL API covering core transcript/meeting data (queries, transcript details, uploadAudio mutation, audit events) plus MCP servers for docs and data access, showing solid API parity for core recording/transcription/search workflows. However, there's no evidence that UI-only features like the Rules Engine automation, admin Super Admin controls, AskFred AI assistant, or multi-language mode settings are exposed via the API, so full UI/API parity isn't demonstrated. Missing for 10: API endpoints for Rules Engine/admin automation, AskFred assistant interactions, and language-mode configuration.

   • [claimed-docs] “The `uploadAudio` mutation allows you to upload audio files to Fireflies.ai for transcription.”
   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “The transcript query is designed to fetch details associated with a specific transcript ID.”
   • [claimed-docs] “Audit Logs ([API](https://docs.fireflies.ai/graphql-api/query/audit-events#audit-events))”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “AskFred: AI assistant”
   • [probe] “PROBE runtime (recorded 2026-09-05): a keyless GraphQL query POSTed to the live endpoint https://api.fireflies.ai/graphql returned the docum…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Fireflies.ai
   Fireflies.ai~partialprobed5/10

   Fireflies exposes a GraphQL API (transcripts/transcript queries) that lets a user programmatically pull structured meeting data in JSON, and this is confirmed live and reachable in the runtime probe, giving a technical path to self-export. However, there is no documented bulk 'export all my data' feature, no mention of standard open export formats (CSV/JSON dump, GDPR-style account export), and no evidence of a data-portability or account-deletion export workflow for someone wanting to fully leave the platform. missing for 10: a documented full-account data export/portability feature, explicit open-format (CSV/JSON) bulk export tool, and evidence of an easy 'leave and take everything' workflow beyond ad-hoc API queries.

   • [claimed-docs] “The transcripts query is designed to fetch a list of transcripts against input arguments.”
   • [claimed-docs] “The transcript query is designed to fetch details associated with a specific transcript ID.”
   • [claimed-docs] “The Fireflies API is built on top of GraphQL... This API allows you to retrieve exactly the data you need in a structured format.”
   • [probe] “PROBE runtime (recorded 2026-09-05): a keyless GraphQL query POSTed to the live endpoint https://api.fireflies.ai/graphql returned the docum…”

   proof ↗⚑ flag

   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

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
   Fireflies.ai~partialclaimed4/10

   The pricing page evidently lists concrete feature differentiators per tier (e.g., AskFred, real-time notes, audit logs, multi-language mode, team analytics) suggesting a self-serve, itemized pricing page rather than a sales-only wall, but the pack never shows actual dollar figures, an explicit 'Free' plan, or a statement confirming no sales contact is required for basic use. missing for 10: explicit free-tier existence/limits, listed price points per tier, and confirmation that upgrading doesn't require contacting sales.

   • [claimed-docs] “Audit Logs ([API](https://docs.fireflies.ai/graphql-api/query/audit-events#audit-events))”
   • [claimed-docs] “AskFred: AI assistant”
   • [claimed-docs] “Real-time notes & live transcriptions”
   • [claimed-docs] “Private Storage on Enterprise to store your meeting data at your preferred location.”
   • [claimed-docs] “Conversation intelligence Team analytics (for admins)”
   • [claimed-docs] “Multi-language Mode”

   proof ↗⚑ flag

   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

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 to Fireflies.ai
   Fireflies.ai~partialclaimed3/10

   Fireflies documents admin-side privacy controls (a 'Rules Engine' for automation workflows governing meeting access/privacy, and Super Admin access controls) which give IT admins some enforced transparency levers, but there is no evidence of actual participant-facing consent mechanics — no documented in-meeting recording announcement, join notification, or consent banner beyond the bot ('Fred') simply appearing in the call as an implicit signal. missing for 10: explicit in-meeting disclosure/announcement feature, participant notification settings, and any documentation framing these as consent/compliance tools rather than generic access-control automation.

   • [claimed-docs] “Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record, transcribe, and summarize.”
   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Full meeting access to your entire workspace by upgrading to Super Admin status.”

   proof ↗⚑ flag

   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

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
   Fireflies.ai—none0/10

   The evidence pack includes Fireflies security-page snippets (private storage, rules engine, audit logs) but contains no mention of whether meeting data is used to train AI models, no documented opt-out mechanism, and no SOC 2 or HIPAA certification claims. This axis is fair for a meeting-recording SaaS handling sensitive conversation data, but no supporting evidence exists in the pack.

   • [claimed-docs] “Audit Logs ([API](https://docs.fireflies.ai/graphql-api/query/audit-events#audit-events))”
   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Private Storage on Enterprise to store your meeting data at your preferred location.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Secure, dedicated cloud storage exclusively for your organization’s data.”

   proof ↗⚑ flag

   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

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

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

   Evidence shows admin-facing security/automation features (Rules Engine, Private Storage, Super Admin access) but no mention of configurable data retention schedules, auto-delete of transcripts/recordings, or an on-demand permanent erasure capability.

   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Private Storage on Enterprise to store your meeting data at your preferred location.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Full meeting access to your entire workspace by upgrading to Super Admin status.”
   • [claimed-docs] “Secure, dedicated cloud storage exclusively for your organization’s data.”

   proof ↗⚑ flag

   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

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

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

   Fireflies documents Enterprise-tier 'Private Storage' to store meeting data at a preferred location and 'Secure, dedicated cloud storage exclusively for your organization's data,' directly addressing data residency choice, but this is gated to a specific plan with no detail on which regions are supported or how selection is configured. Missing for 10: list of available regions, self-serve UI/API for setting residency, independent/hands-on confirmation of the feature working as described.

   • [claimed-docs] “Private Storage on Enterprise to store your meeting data at your preferred location.”
   • [claimed-docs] “Secure, dedicated cloud storage exclusively for your organization’s data.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Otter.ai
   Fireflies.ai—none0/10

   No evidence pack item addresses AI-model-training opt-out or data-use-for-training policy; security/privacy pages mention private storage and access controls but never mention AI training exclusion.

   ⚑ flag

   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

3. ai-native userControl data retention and deletion

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

   The evidence pack shows security/privacy features like private storage location, admin access rules, and audit logs, but nowhere documents a data retention policy, a deletion API/mutation, or user-controlled data purging (e.g., no deleteTranscript mutation or retention settings in the GraphQL API docs).

   ⚑ flag

   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

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

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

   No evidence pack item mentions telemetry opt-out, usage tracking controls, or analytics disabling for Fireflies.ai itself; the closest items relate to admin privacy controls, storage location, and audit logs, not user-level telemetry opt-out.

   ⚑ flag

   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

Sharing

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

   weight 1 · round drawn
   Fireflies.ai—none0/10

   The evidence pack contains no mention of a soundbite/clip-cutting or highlight-sharing feature for calls—only API/GraphQL docs, MCP server details, transcription, and general meeting summary features are documented.

   ⚑ flag

   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

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 Fireflies.ai
   Fireflies.ai~partialclaimed6/10

   Fireflies documents real admin-facing sharing controls: a Rules Engine for automating meeting access/privacy, Super Admin status for full workspace visibility, and an Audit Logs API for tracking activity, plus Enterprise private/dedicated storage. However there's no explicit documentation of private-by-default note settings or granular per-link/per-folder permission structures. missing for 10: explicit private-by-default note policy, granular link/folder-level permission docs, independent/hands-on verification of admin visibility features.

   • [claimed-docs] “Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Rules Engine Automation workflows for admins to have control over meeting access and privacy.”
   • [claimed-docs] “Full meeting access to your entire workspace by upgrading to Super Admin status.”
   • [claimed-docs] “Audit Logs ([API](https://docs.fireflies.ai/graphql-api/query/audit-events#audit-events))”
   • [claimed-docs] “Secure, dedicated cloud storage exclusively for your organization’s data.”
   • [claimed-docs] “Private Storage on Enterprise to store your meeting data at your preferred location.”

   proof ↗⚑ flag

   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

Transcription

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

   weight 2 · round to Fireflies.ai
   Fireflies.ai~partialclaimed5/10

   Fireflies advertises automatic language switching between meetings and a paid 'Multi-language Mode' add-on, indicating some multilingual support, but there's no documentation of which languages are supported, accuracy across languages, or how mid-meeting switching/code-switching is handled, and no independent corroboration. missing for 10: list of supported languages, accuracy benchmarks per language, handling of code-switching within a single meeting, and third-party validation of multilingual transcription quality.

   • [claimed-docs] “Automatically switch languages from meeting to meeting with ease.”
   • [claimed-docs] “Multi-language Mode”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Fireflies.ai~partialclaimed4/10

   Fireflies docs claim it 'identifies different speakers in meetings and audio files' (diarization), but there is no evidence detailing how it maps names to speaker labels (e.g., via calendar invitee matching or voice enrollment) or accuracy data. missing for 10: documentation on real-name matching mechanism, accuracy benchmarks, and independent/hands-on verification of correct name attribution.

   • [claimed-docs] “Fireflies identifies different speakers in meetings and audio files.”

   proof ↗⚑ flag

   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

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
   Fireflies.ai—none0/10

   The evidence pack shows marketing feature claims (speaker ID, multi-language, live transcription) and API docs, but nowhere documents the underlying transcription model, accuracy/WER benchmarks, or known limitations of the transcription engine itself — it is generic 'AI-powered' framing rather than the technical transparency the story asks for.

   • [claimed-docs] “Invite fred@fireflies.ai to a live meeting or have it autojoin your calendar meetings to record, transcribe, and summarize.”
   • [claimed-docs] “Automatically switch languages from meeting to meeting with ease.”
   • [claimed-docs] “Fireflies identifies different speakers in meetings and audio files.”
   • [claimed-docs] “Automatically record your Google Meet calls and get real-time transcripts.”
   • [claimed-docs] “Multi-language Mode”

   proof ↗⚑ flag

   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