Granola vs Fathom

Agent ops

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

   weight 2 · round to Fathom
   Granola~partialprobed5/10

   Granola offers a documented API/MCP server for programmatic access to meeting notes and a Zapier integration claiming 8,000+ app connections to 'automate what happens after a meeting,' which could route action items to Linear/Jira/Asana, and a native HubSpot sync exists as a precedent for native two-way automation. However, there is no documented native integration or pre-built automation specifically for Linear/Jira/Asana, and MCP/Chat tools shown (search notes, draft email/Slack, calendar events) are read/communication-focused rather than ticket-filing into project trackers. Missing for 10: a documented native Linear/Jira/Asana integration or explicit Zapier recipe/template for action-item ticket creation, and evidence of webhook-triggered ticket creation in these specific trackers.

   • [claimed-docs] “Connect Granola to 8,000+ apps and automate what happens after a meeting”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP.”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”
   • [claimed-docs] “Sync Granola meeting notes to HubSpot. Automatically sync notes to CRM records from your meetings using folders.”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Granola✓fullprobed9/10

   Granola documents an official hosted MCP server (mcp.granola.ai) supporting search, transcripts, and meeting queries, and a runtime probe confirms the endpoint is live and enforces OAuth via the standard MCP protected-resource flow (401 + WWW-Authenticate pointing to oauth-protected-resource metadata), matching the story's OAuth/no-glue-code requirement. Missing for 10: independent third-party (non-vendor) hands-on confirmation of a successful end-to-end OAuth connection and action-item retrieval.

   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP.”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes,…”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Fathom
   Granola~partialprobed7/10

   Granola docs confirm a documented REST API for programmatic access to meeting notes, transcripts, and AI summaries (granola-docs-1,16,33,34), and reference both individual and workspace-level API keys, implying self-serve key generation (granola-docs-28). However, action items are not explicitly called out as a retrievable field, and a probe found no live OpenAPI/swagger spec, suggesting the API reference may be thin or beta (granola-probe-2). missing for 10: explicit documentation of action-item extraction, a public OpenAPI/schema reference, and independent developer corroboration of successful API key self-service and querying.

   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data.”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”
   • [claimed-docs] “Custom AI agents - Build agents that analyze sentiment across your calls, surface recurring themes in product feedback, or combine meeting c…”
   • [claimed-docs] “Workspace admins on Business and Enterprise plans can also create workspace API keys. These belong to the workspace rather than an individua…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.granola.ai/openapi.json, https://docs.granola.ai/swagger.json, https://docs.granola.ai/…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

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

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

   proof ↗⚑ flag

Agent access

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

   weight 2 · round drawn
   Granola✓fullprobed9/10

   A live llms.txt is confirmed via direct HTTP probe (200 OK) at docs.granola.ai/llms.txt, and Granola also documents agent-oriented resources (API for custom agents, an official OAuth-protected MCP server verified live via runtime probe), giving agents multiple discoverable, machine-readable entry points into Granola's docs and data. Missing for 10: no independent/community confirmation of an agent actually consuming llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.granola.ai/llms.txt # Granola Docs & Help Center - [Granola Help Center](https://docs.granola.ai/h…”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [claimed-docs] “Custom AI agents - Build agents that analyze sentiment across your calls, surface recurring themes in product feedback, or combine meeting c…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Fathom
   Granola~partialprobed3/10

   Granola exposes a REST API and an MCP server for programmatic access to meeting notes/transcripts, which could be scripted into automated pipelines, but the core product is a desktop app that captures live meeting audio and there is no documented CLI, headless mode, or CI-specific workflow. Missing for 10: explicit headless/CI execution mode, CLI tooling, and any example of running Granola non-interactively in an automation pipeline.

   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data.”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Granola—none0/10

   All evidence describes Granola exposing its own MCP server (and API) so other AI tools can pull Granola's meeting data — the reverse of the story, which asks whether Granola itself can consume external MCP servers as a client to gain new tools. No evidence shows Granola's Chat or any other feature accepting/plugging in third-party MCP servers.

   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP.”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes,…”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”

   proof ↗⚑ flag

   Fathom—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Fathom
   Granola✓fullprobed8/10

   Granola documents an official MCP server ('Granola MCP') for connecting AI tools/agents to meeting notes (search, list_meetings, get_meeting_transcript, query_granola_meetings), and a runtime probe confirms the hosted endpoint https://mcp.granola.ai/mcp is live and correctly speaks MCP's OAuth-protected resource flow. Missing for 10: independent/community hands-on confirmation of a successful agent connection beyond the vendor docs and probe.

   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP.”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes,…”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Fathom
   Granola✓fullprobed7/10

   Granola documents a RESTful public API for programmatic access to meeting notes, transcripts, and summaries, including workspace-level API keys for admins, and a live official MCP server (confirmed via runtime probe) that supports OAuth-based agent access to meeting data. This is solid documented evidence of API-driven, agentic use of the product beyond the base app UI. Missing for 10: a formal OpenAPI/reference spec (probe found 404s for openapi.json/swagger.json) and independent third-party developer reports validating real-world API integration.

   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”
   • [claimed-docs] “Workspace admins on Business and Enterprise plans can also create workspace API keys. These belong to the workspace rather than an individua…”
   • [claimed-docs] “Custom AI agents - Build agents that analyze sentiment across your calls, surface recurring themes in product feedback, or combine meeting c…”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.granola.ai/openapi.json, https://docs.granola.ai/swagger.json, https://docs.granola.ai/…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Granola—none0/10

   Granola documents API keys (personal and workspace-level) and an OAuth-based MCP server, but there is no evidence of scoped or least-privilege credential issuance — e.g., no read-only vs write scopes, no per-agent permission granularity, and workspace keys are described as broad and non-expiring rather than restrictable.

   • [claimed-docs] “Workspace admins on Business and Enterprise plans can also create workspace API keys. These belong to the workspace rather than an individua…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”

   proof ↗⚑ flag

   Fathom—none0/10

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

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

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Fathom
   Granola~partialprobed5/10

   Granola exposes a documented RESTful API and an official hosted MCP server (confirmed live via runtime probe with OAuth), which lets AI-native users build custom agents/integrations, but there is no evidence of official language SDKs, client libraries, or a discoverable OpenAPI/swagger spec (probe found only 404s). Missing for 10: published SDKs in common languages, an OpenAPI spec, and independent developer corroboration of building against the API.

   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”
   • [claimed-docs] “Custom AI agents - Build agents that analyze sentiment across your calls, surface recurring themes in product feedback, or combine meeting c…”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.granola.ai/openapi.json, https://docs.granola.ai/swagger.json, https://docs.granola.ai/…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

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

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

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Fathom
   Granola—none0/10

   Evidence covers a REST API, MCP server, Zapier/HubSpot integrations, and chat workflows, but nothing in the pack describes any webhook subscription mechanism for event notifications. Zapier could theoretically enable trigger-based automation, but no documentation confirms Granola exposes outbound webhooks for developers to subscribe to events directly. missing for 10: documented webhook endpoints, event types, subscription/registration mechanism, payload schema.

   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [claimed-docs] “Connect Granola to 8,000+ apps and automate what happens after a meeting”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.granola.ai/openapi.json, https://docs.granola.ai/swagger.json, https://docs.granola.ai/…”

   proof ↗⚑ flag

   Fathom✓fullprobed9/10

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

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

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Granola✓fullclaimed8/10

   Granola Chat lets users ask questions and get instant AI-generated insights, spot patterns across calls, and generate follow-up outputs directly inside the product, with Recipes providing reusable insight-generating prompt templates. This is native, first-party AI-native functionality well documented across multiple docs pages. Missing for 10: independent/hands-on validation of insight quality and accuracy beyond vendor docs.

   • [claimed-docs] “Chat with your meeting notes to recall meeting details, spot patterns across customer calls, and generate follow-up outputs.”
   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting... draft and send a follow-up email”
   • [claimed-docs] “Recipes are reusable prompt templates that help you quickly get insights from your meeting notes without typing the same questions repeatedl…”
   • [claimed-docs] “Granola Chat lets you ask questions about your meetings and get instant insights from your notes or transcripts.”
   • [claimed-docs] “draft and send a follow-up email" ... "draft and send a Slack message" ... "find a time and create a Google Calendar event”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”
   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting, without switching between your notes and other apps.”

   proof ↗⚑ flag

   Fathom✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Granola~partialprobed5/10

   Granola supports automations that fire after meetings via Zapier (8,000+ app connections) and HubSpot auto-sync, and offers an API/MCP server for building custom 'agents' that analyze calls—these run without manual intervention once configured. However, there's no evidence of a native scheduler or persistent background agent loop inside Granola itself; the 'autonomy' comes from third-party automation platforms (Zapier/HubSpot) or requires the user to build their own agent via API/MCP rather than Granola running one natively. Missing for 10: native in-app automation/scheduling engine, evidence of continuously running background agents (not just event-triggered post-meeting syncs), and independent confirmation these automations run reliably unattended.

   • [claimed-docs] “Connect Granola to 8,000+ apps and automate what happens after a meeting”
   • [claimed-docs] “Sync Granola meeting notes to HubSpot. Automatically sync notes to CRM records from your meetings using folders.”
   • [claimed-docs] “You can set up Granola to automatically save any notes that are added to Granola folders to the relevant contacts, companies, or deals on Hu…”
   • [claimed-docs] “Custom AI agents - Build agents that analyze sentiment across your calls, surface recurring themes in product feedback, or combine meeting c…”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”

   proof ↗⚑ flag

   Fathom~partialprobed5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Granola
   Granola✓fullclaimed7/10

   Granola ships a built-in 'Granola Chat' assistant that users can delegate post-meeting tasks to, e.g. drafting and sending follow-up emails/Slack messages and creating calendar events directly from meeting notes, plus reusable 'Recipes' prompt templates for repeated tasks. This is documented across multiple first-party doc pages describing concrete agentic actions triggered from chat. Missing for 10: independent/hands-on verification that these delegated actions (sending email, creating calendar events) actually execute reliably, and more detail on assistant autonomy/error-handling beyond vendor docs.

   • [claimed-docs] “Chat with your meeting notes to recall meeting details, spot patterns across customer calls, and generate follow-up outputs.”
   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting... draft and send a follow-up email”
   • [claimed-docs] “Granola Chat lets you ask questions about your meetings and get instant insights from your notes or transcripts.”
   • [claimed-docs] “draft and send a follow-up email" ... "draft and send a Slack message" ... "find a time and create a Google Calendar event”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”
   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting, without switching between your notes and other apps.”
   • [claimed-docs] “Recipes are reusable prompt templates that help you quickly get insights from your meeting notes without typing the same questions repeatedl…”

   proof ↗⚑ flag

   Fathom~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Granola
   Granola✓fullclaimed7/10

   Granola Chat lets users interact via natural-language queries to recall meeting details, spot patterns, and trigger actions like drafting/sending a follow-up email, drafting a Slack message, or creating a calendar event—clear NL-command operation within the product. missing for 10: independent/hands-on corroboration of chat-driven command execution, and detail on reliability/limits of the NL command surface beyond first-party docs.

   • [claimed-docs] “Chat with your meeting notes to recall meeting details, spot patterns across customer calls, and generate follow-up outputs.”
   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting... draft and send a follow-up email”
   • [claimed-docs] “Granola Chat lets you ask questions about your meetings and get instant insights from your notes or transcripts.”
   • [claimed-docs] “draft and send a follow-up email" ... "draft and send a Slack message" ... "find a time and create a Google Calendar event”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”
   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting, without switching between your notes and other apps.”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

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

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

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Fathom
   Granola—none0/10

   There's a mention of a RESTful API and MCP server, but no evidence of an interactive API reference with runnable examples; probes explicitly show no OpenAPI/swagger spec is exposed (all candidate paths 404), and no docs mention interactive playgrounds or code samples runnable in-browser.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.granola.ai/openapi.json, https://docs.granola.ai/swagger.json, https://docs.granola.ai/…”
   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”

   proof ↗⚑ flag

   Fathom~partialprobed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Fathom
   Granola—none0/10

   Granola documents a REST API and MCP integration but explicit probes show no OpenAPI/Swagger spec is published at any standard location (all candidate paths returned 404), and no machine-readable API spec is referenced anywhere in the docs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.granola.ai/openapi.json, https://docs.granola.ai/swagger.json, https://docs.granola.ai/…”
   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”

   proof ↗⚑ flag

   Fathom✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Granola—none0/10

   The evidence shows a Granola REST API and MCP server exist, but there is no documentation of API versioning scheme or a deprecation policy; an openapi.json probe returned 404s, suggesting no formal API spec/versioning surface is published. missing for 10: versioning scheme documentation, deprecation policy/notice process, changelog or migration guides.

   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.granola.ai/openapi.json, https://docs.granola.ai/swagger.json, https://docs.granola.ai/…”
   • [claimed-docs] “Workspace admins on Business and Enterprise plans can also create workspace API keys. These belong to the workspace rather than an individua…”

   proof ↗⚑ flag

   Fathom—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Granola~partialprobed4/10

   Granola offers bulk *export* of all notes to CSV and API/MCP access that can read across the whole workspace (search, list_meetings), which supports bulk analysis, but there's no documented capability for bulk mutating operations (e.g., batch delete, batch re-tag, batch share) across many items at once. missing for 10: explicit bulk write/update operations, batch API endpoints for multi-item actions, evidence of an agent actually performing such an operation.

   • [claimed-docs] “Export your Granola meeting notes to CSV. Get note titles, summaries, transcripts, and details.”
   • [claimed-docs] “You're able to export historical data from Granola by going to Settings, clicking Profile in the sidebar (under Preferences), and clicking G…”
   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data. This RESTful API enables you to integrate G…”
   • [probe] “official MCP server documented at https://docs.granola.ai/help-center/sharing/integrations/mcp”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”

   proof ↗⚑ flag

   Fathom~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Fathom
   Granola~partialclaimed4/10

   Granola supports event-triggered automation only via third-party integrations: Zapier (8,000+ apps, 'automate what happens after a meeting') and HubSpot folder-based auto-sync ('automatically save any notes added to Granola folders to relevant contacts/deals'). These act as rule-like triggers but are not a native in-product rules/automation engine, and Chat 'workflows' are manually invoked rather than event-triggered. Missing for 10: a native rules/automation builder within Granola itself, documentation of custom trigger-condition-action definitions, and evidence of broader event types beyond folder-add/meeting-end.

   • [claimed-docs] “Connect Granola to 8,000+ apps and automate what happens after a meeting”
   • [claimed-docs] “You can set up Granola to automatically save any notes that are added to Granola folders to the relevant contacts, companies, or deals on Hu…”
   • [claimed-docs] “Automatically sync notes to CRM records from your meetings using folders.”
   • [claimed-docs] “draft and send a follow-up email" ... "draft and send a Slack message" ... "find a time and create a Google Calendar event”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Granola—none0/10

   Evidence shows Granola offers APIs, MCP, Zapier/HubSpot integrations, and one-off Chat workflows (draft emails, Slack messages, calendar events), but nothing describes scheduling recurring jobs or automated workflows to run on a cadence within Granola itself — recurring automation would rely entirely on third-party tools like Zapier, not a native Granola feature.

   • [claimed-docs] “Connect Granola to 8,000+ apps and automate what happens after a meeting”
   • [claimed-docs] “draft and send a follow-up email" ... "draft and send a Slack message" ... "find a time and create a Google Calendar event”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [claimed-docs] “Custom AI agents - Build agents that analyze sentiment across your calls, surface recurring themes in product feedback, or combine meeting c…”

   proof ↗⚑ flag

   Fathom—none0/10

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

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

   proof ↗⚑ flag

Calendar

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

   weight 3 · round drawn
   Granola—none0/10

   Evidence shows Granola connects to a calendar to display upcoming meetings and offers templates per call type for note formatting, but there is no mention of per-meeting-type rules controlling which meetings get automatically captured/recorded — no filtering, auto-join rules, or selective-capture settings are documented.

   • [claimed-docs] “Granola connects to your calendar to show your upcoming meetings.”
   • [claimed-docs] “you might want to choose a specific template (or set up your own!) for a specific type of call: for instance, 1:1s, interviews or sales pitc…”
   • [claimed-docs] “you might want to choose a specific template (or set up your own!) for a specific type of call: for instance, 1:1s, interviews or sales pitc…”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 1 · round to Granola
   Granola~partialclaimed4/10

   Granola stores meeting notes/transcripts and lets users search or chat with past notes (via Chat or MCP's 'search through your meeting notes, find specific topics discussed in past meetings'), and it connects to your calendar to show upcoming meetings, which together could support manual meeting prep. However, there is no evidence of an automatic pre-call brief or a feature that proactively surfaces past meetings with the same attendees before a call starts — the burden is on the user to search/chat manually. Missing for 10: automatic surfacing of past meetings by attendee tied to calendar events, a dedicated pre-meeting briefing/open-threads summary feature, and any first-hand account of this proactive workflow.

   • [claimed-docs] “Granola connects to your calendar to show your upcoming meetings.”
   • [claimed-docs] “Granola Chat lets you ask questions about your meetings and get instant insights from your notes or transcripts.”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes,…”
   • [claimed-docs] “Chat with your meeting notes to recall meeting details, spot patterns across customer calls, and generate follow-up outputs.”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

Capture

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

   weight 2 · round to Granola
   Granola✓fullcommunity8/10

   Granola explicitly claims to work with Zoom, Google Meet, Teams and other apps, and records via computer audio rather than a bot joining the call, directly addressing the 'recording where I want it' preference. Community evidence corroborates real-world reliability (battery/performance) and PM usage, though no independent side-by-side accuracy test across all three platforms is present. Missing for 10: independent verification of capture reliability across each specific platform (Zoom/Meet/Teams) and no mention of optional bot-based recording for cases where computer-audio capture isn't desired.

   • [claimed-docs] “Works with Zoom, Google Meet, Teams and every other meeting app.”
   • [claimed-docs] “Uses your computer audio, so doesn't invite a bot”
   • [community] “I've been beta testing it and it seems like it's not bad for battery life at all, works like a charm.”
   • [community] “I work as a PM and have a lot of calls and action items that tend to slip through so I've built a Mac app that turns Granola calls into a ka…”

   proof ↗⚑ flag

   Fathom~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Granola
   Granola✓fullcommunity9/10

   Granola's core value prop is capturing device/computer audio directly without a bot joining the call, explicitly stated as 'Uses your computer audio, so doesn't invite a bot' and works across Zoom/Meet/Teams/etc, with transparency messaging posted in chat rather than a visible bot presence. Community evidence corroborates it runs quietly in the background on the user's device. Missing for 10: independent hands-on confirmation from a founder-specific use case and no explicit contradicting report of a visible bot ever appearing.

   • [claimed-docs] “Uses your computer audio, so doesn't invite a bot”
   • [claimed-docs] “Works with Zoom, Google Meet, Teams and every other meeting app.”
   • [claimed-docs] “Granola posts a message in your meeting chat when it starts transcribing to let everyone know.”
   • [community] “Granola terrifies me. It’s highly capable at summarisation, and seems to be free. What’s the catch? ... it runs in the background on my Mac,…”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Granola
   Granola~partialclaimed6/10

   Granola's docs confirm a mobile app for recording AI-enhanced notes during in-person meetings and iOS calls, and separate docs confirm workspace-wide search/chat over meeting notes, but no evidence explicitly ties mobile-captured notes into the same searchable workspace pipeline. missing for 10: explicit confirmation that mobile-recorded notes/transcripts sync into the same workspace and are searchable via Chat/API alongside desktop notes, and any hands-on user report validating this integration.

   • [claimed-docs] “Granola for mobile lets you take AI-enhanced notes during in-person meetings (and, on iOS, phone calls).”
   • [claimed-docs] “Granola Chat lets you ask questions about your meetings and get instant insights from your notes or transcripts.”
   • [claimed-docs] “Use the magnifying glass beside each note to see where in the transcript or raw notes the note came from”
   • [claimed-docs] “Granola connects to your calendar to show your upcoming meetings.”

   proof ↗⚑ flag

   Fathom—none0/10

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

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

   proof ↗⚑ flag

Integrations

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

   weight 3 · round to Granola
   Granola~partialclaimed6/10

   Granola has a documented native HubSpot integration that auto-syncs meeting notes to the correct contacts, companies, and deals via folders (granola-docs-10, granola-docs-39), which directly matches the story for HubSpot. However, there is no dedicated Salesforce or Attio integration documented — those CRMs would only be reachable indirectly via the generic Zapier connector (granola-docs-9), not a first-party record-matching sync. Missing for 10: explicit native Salesforce and Attio CRM sync with contact/deal matching, and independent/hands-on confirmation that the HubSpot sync reliably attaches to the 'right' record.

   • [claimed-docs] “Sync Granola meeting notes to HubSpot. Automatically sync notes to CRM records from your meetings using folders.”
   • [claimed-docs] “Automatically sync notes to CRM records from your meetings using folders.”
   • [claimed-docs] “You can set up Granola to automatically save any notes that are added to Granola folders to the relevant contacts, companies, or deals on Hu…”
   • [claimed-docs] “Connect Granola to 8,000+ apps and automate what happens after a meeting”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Granola
   Granola✓fullclaimed8/10

   Granola explicitly documents Zapier integration to 8,000+ apps, native HubSpot CRM sync, and Chat workflows that draft/send Slack messages and follow-up emails, directly matching the story's 'flows into Slack, Notion, and thousands of apps' vision. Notion isn't named directly, but it would be covered under the 8,000+ app Zapier ecosystem; missing for 10: an explicit first-party Notion integration/doc and independent user confirmation that Slack/Notion syncing works reliably in practice.

   • [claimed-docs] “Connect Granola to 8,000+ apps and automate what happens after a meeting”
   • [claimed-docs] “Sync Granola meeting notes to HubSpot. Automatically sync notes to CRM records from your meetings using folders.”
   • [claimed-docs] “Automatically sync notes to CRM records from your meetings using folders.”
   • [claimed-docs] “draft and send a follow-up email" ... "draft and send a Slack message" ... "find a time and create a Google Calendar event”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”
   • [claimed-docs] “You can set up Granola to automatically save any notes that are added to Granola folders to the relevant contacts, companies, or deals on Hu…”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

Memory

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

   weight 2 · round to Granola
   Granola✓fullprobed7/10

   Granola Chat explicitly lets users ask natural-language questions across meeting notes/transcripts and get insights, with a magnifying-glass feature to trace an answer back to its source location in the transcript/notes, and the MCP/API integrations further support searching past meetings and surfacing sourced context. missing for 10: independent/hands-on validation of answer accuracy and citation quality, and explicit confirmation that native Chat (not just MCP) searches the *entire* historical corpus rather than per-meeting.

   • [claimed-docs] “Granola Chat lets you ask questions about your meetings and get instant insights from your notes or transcripts.”
   • [claimed-docs] “Chat with your meeting notes to recall meeting details, spot patterns across customer calls, and generate follow-up outputs.”
   • [claimed-docs] “Use the magnifying glass beside each note to see where in the transcript or raw notes the note came from”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes,…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Granola
   Granola✓fullprobed8/10

   Granola Chat lets users ask questions and get insights across notes/transcripts (docs-19, docs-4), the MCP server explicitly supports searching through meeting notes and finding topics across past meetings plus retrieving full transcripts (docs-35, granola-probe-rt-1), and the in-app magnifying-glass feature jumps to the exact transcript/note location a note came from (docs-27). Missing for 10: independent/hands-on evidence confirming true cross-meeting semantic search quality (vs. single-note context) and no explicit documentation of a dedicated 'search all meetings' UI beyond Chat/MCP.

   • [claimed-docs] “Granola Chat lets you ask questions about your meetings and get instant insights from your notes or transcripts.”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes,…”
   • [claimed-docs] “Use the magnifying glass beside each note to see where in the transcript or raw notes the note came from”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”
   • [claimed-docs] “Chat with your meeting notes to recall meeting details, spot patterns across customer calls, and generate follow-up outputs.”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

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

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

   proof ↗⚑ flag

Summaries

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

   weight 3 · round to Fathom
   Granola—none0/10

   Granola's docs describe general AI summaries, chat Q&A, and workflow actions (draft follow-up emails, Slack messages, calendar events) but never mention structured action-item extraction with assigned owners or a dedicated tracking view/list. Community evidence reinforces this gap: a PM explicitly built a separate third-party app to turn Granola meeting notes into a kanban to-do list because action items 'tend to slip through' natively.

   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting... draft and send a follow-up email”
   • [claimed-docs] “draft and send a follow-up email" ... "draft and send a Slack message" ... "find a time and create a Google Calendar event”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”
   • [community] “I work as a PM and have a lot of calls and action items that tend to slip through so I've built a Mac app that turns Granola calls into a ka…”

   proof ↗⚑ flag

   Fathom✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Granola
   Granola✓fullclaimed8/10

   Granola explicitly supports custom/default templates per call type (1:1s, interviews, sales pitches) and 'Recipes' as reusable prompt templates to avoid retyping the same questions, directly matching the story's need for per-meeting-type customization. Missing for 10: independent/hands-on user corroboration of template customization quality and confirmation that saved 'recipes' can be tied to specific meeting types automatically.

   • [claimed-docs] “you might want to choose a specific template (or set up your own!) for a specific type of call: for instance, 1:1s, interviews or sales pitc…”
   • [claimed-docs] “you might want to choose a specific template (or set up your own!) for a specific type of call: for instance, 1:1s, interviews or sales pitc…”
   • [claimed-docs] “While Granola's default summarisation adapts to a range of formats, you might want to choose a specific template (or set up your own!) for a…”
   • [claimed-docs] “Recipes are reusable prompt templates that help you quickly get insights from your meeting notes without typing the same questions repeatedl…”

   proof ↗⚑ flag

   Fathom—none0/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to Granola
   Granola✓fullclaimed8/10

   Granola Chat explicitly supports drafting and sending a follow-up email directly from meeting notes as a documented workflow, with sales-relevant templates (e.g., sales pitch note templates) and CRM sync options for follow-through. Missing for 10: no independent/hands-on review confirming the 'couple of clicks' review-and-send UX in practice, and no detail on how much editing/review is typically needed before sending.

   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting... draft and send a follow-up email”
   • [claimed-docs] “draft and send a follow-up email" ... "draft and send a Slack message" ... "find a time and create a Google Calendar event”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”
   • [claimed-docs] “Granola Chat can help you complete the work that comes after a meeting, without switching between your notes and other apps.”
   • [claimed-docs] “you might want to choose a specific template (or set up your own!) for a specific type of call: for instance, 1:1s, interviews or sales pitc…”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 3 · round drawn
   Granola✓fullclaimed7/10

   Granola's core AI-enhanced notes produce structured summaries with templates for different meeting types (1:1s, interviews, sales pitches), speaker attribution, and searchable source-linked notes, which are shareable via link or CSV export without further editing. missing for 10: independent hands-on evaluation of summary quality/accuracy (e.g., a reviewer confirming it required no edits), and no direct evidence addressing 'decisions' and 'next steps' as distinct structured fields versus a general summary format.

   • [claimed-docs] “you might want to choose a specific template (or set up your own!) for a specific type of call: for instance, 1:1s, interviews or sales pitc…”
   • [claimed-docs] “you might want to choose a specific template (or set up your own!) for a specific type of call: for instance, 1:1s, interviews or sales pitc…”
   • [claimed-docs] “While Granola's default summarisation adapts to a range of formats, you might want to choose a specific template (or set up your own!) for a…”
   • [claimed-docs] “Speaker tags show each participant's name above their parts of the conversation, giving you more detailed attribution than the default Me an…”
   • [claimed-docs] “Use the magnifying glass beside each note to see where in the transcript or raw notes the note came from”
   • [claimed-docs] “Copy link will copy a unique URL link to the meeting notes, which you can send to others.”
   • [claimed-docs] “The CSV includes the title, note summary, transcript, and other basic details for each note.”

   proof ↗⚑ flag

   Fathom✓fullclaimed7/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Fathom
   Granola~partialprobed4/10

   The Granola API and MCP server give programmatic read access to meeting notes, transcripts, and summaries, and support building custom agents (granola-docs-1/16/34/35, granola-probe-rt-1 confirms live OAuth MCP endpoint), but there's no documented API endpoint for the many interactive UI capabilities like Chat workflows (draft/send email, Slack, calendar events), Recipes/templates, folder-based CRM sync, or transcript auto-deletion settings — these remain UI-only or handled via separate third-party integrations (Zapier/HubSpot). No OpenAPI spec was found (granola-probe-2 shows 404s), suggesting a narrow, undocumented surface rather than full UI parity. Missing for 10: API endpoints for chat-driven actions, template/recipe management via API, and any documented parity for sharing/export settings.

   • [claimed-docs] “The Granola API provides programmatic access to your workspace's meeting notes and related data.”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [claimed-docs] “Custom AI agents - Build agents that analyze sentiment across your calls, surface recurring themes in product feedback, or combine meeting c…”
   • [claimed-docs] “Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes,…”
   • [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://mcp.granola.ai/mcp returned …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.granola.ai/openapi.json, https://docs.granola.ai/swagger.json, https://docs.granola.ai/…”
   • [claimed-docs] “Ask Chat to: draft and send a follow-up email * draft and send a Slack message * find a time and create a Google Calendar event”
   • [claimed-docs] “Recipes are reusable prompt templates that help you quickly get insights from your meeting notes without typing the same questions repeatedl…”

   proof ↗⚑ flag

   Fathom~partialprobed5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Fathom
   Granola~partialcommunity5/10

   Granola documents a CSV export of meeting notes (titles, summaries, transcripts) via Settings, plus API/MCP access to notes data, giving a real open-format export path, but this covers only notes/transcripts, not a full account/data export (templates, folders, integration settings, chat history) that would let a user fully leave with everything. Community commentary also frames export as a manual workaround ('copy-paste note summaries out to Obsidian') rather than a first-class 'export everything' feature. Missing for 10: comprehensive full-account export beyond notes/transcripts, and any independent confirmation that exported CSV/API data is truly complete and portable.

   • [claimed-docs] “The CSV includes the title, note summary, transcript, and other basic details for each note.”
   • [claimed-docs] “Export your Granola meeting notes to CSV. Get note titles, summaries, transcripts, and details.”
   • [claimed-docs] “You're able to export historical data from Granola by going to Settings, clicking Profile in the sidebar (under Preferences), and clicking G…”
   • [claimed-docs] “This doc walks through how you can export your meeting notes from Granola, including transcripts.”
   • [claimed-docs] “The Granola API lets you build custom integrations with programmatic access to meeting notes, transcripts, and AI summaries.”
   • [community] “It's free for a limited number of notes. I guess you could copypaste the note summaries out to Obsidian or something, but at that point you'…”

   proof ↗⚑ flag

   Fathom~partialprobed6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Granola—none0/10

   Granola is closed-source proprietary software; no evidence pack item mentions open-sourcing the app or any open license for its source code — all evidence covers APIs, integrations, and app features, not source availability.

   ⚑ flag

   Fathom—none0/10

   Fathom is a closed-source SaaS product; the evidence pack shows only API/SDK/MCP documentation and pricing, with no mention of any open-source license or publicly readable source repository for the core product.

   ⚑ 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 to Fathom
   Granola—none0/10

   No evidence pack content addresses Granola's pricing tiers, free plan limits, or paid plan costs/features; only community comments vaguely mention 'free for a limited number of notes' without detail on tier costs or sales-contact requirements. missing for 10: pricing page details, tier breakdown, cost transparency documentation, confirmation of no 'talk to sales' wall.

   • [community] “It's free for a limited number of notes. I guess you could copypaste the note summaries out to Obsidian or something, but at that point you'…”

   proof ↗⚑ flag

   Fathom~partialclaimed4/10

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

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

   proof ↗⚑ flag

Privacy

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

   weight 3 · round to Granola
   Granola~partialclaimed6/10

   Granola documents concrete in-meeting disclosure (a chat message announcing transcription start) and consent-adjacent controls like opting out of model training and auto-deleting transcripts, going beyond a mere policy PDF. However, there is no evidence of admin-enforced transparency settings (e.g., workspace-wide consent policy enforcement, participant opt-out controls, or audit of consent compliance) that would let an IT admin mandate or verify these behaviors across the org. Missing for 10: admin-level enforcement/configuration of consent notifications, participant-side consent management, and any audit trail for consent compliance.

   • [claimed-docs] “Granola posts a message in your meeting chat when it starts transcribing to let everyone know.”
   • [claimed-docs] “You can opt out of model training in Settings.”
   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time.”
   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time. This applies only to transcripts — your notes are not aff…”
   • [claimed-docs] “Your notes are never shared with any participants unless you share the link, or add the note to a folder in your team space.”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 2 · round to Granola
   Granola~partialclaimed4/10

   Granola's docs confirm an opt-out setting for model training (granola-docs-26) and note transparency/consent features like auto-deletion of transcripts and start-of-recording notifications (granola-docs-12, granola-docs-25), but there is no evidence in the pack of SOC 2 or HIPAA compliance documentation, a formal enterprise DPA, or admin-enforced (org-wide) opt-out controls as opposed to per-user settings. Missing for 10: SOC 2/HIPAA certification pages, org-level enforceable opt-out (vs individual toggle), and any compliance/trust-center documentation.

   • [claimed-docs] “You can opt out of model training in Settings.”
   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time.”
   • [claimed-docs] “Granola posts a message in your meeting chat when it starts transcribing to let everyone know.”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 2 · round to Granola
   Granola~partialclaimed5/10

   Docs confirm Granola supports automatic deletion of transcripts after a set period (a scheduled retention policy), but this is framed as a general privacy setting, not clearly an IT-admin-controlled workspace policy, and notes/recordings are explicitly excluded ('your notes are not affected'). There is no evidence of an on-demand 'permanently erase all data' admin action or coverage of audio recordings specifically. Missing for 10: admin-level retention policy management console, recordings deletion (not just transcripts), and an on-demand permanent erase/purge capability.

   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time.”
   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time. This applies only to transcripts — your notes are not aff…”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Granola—none0/10

   No evidence anywhere in the docs or community mentions data residency, regional storage options, or geographic control over where meeting notes/transcripts are stored; only auto-deletion and opt-out-of-training controls are documented, which is a different privacy axis.

   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time.”
   • [claimed-docs] “You can opt out of model training in Settings.”
   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time. This applies only to transcripts — your notes are not aff…”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 3 · round to Granola
   Granola✓fullclaimed8/10

   Granola docs explicitly state users can opt out of model training via Settings, directly delivering the story's core requirement. Missing for 10: independent/hands-on confirmation that opt-out actually stops training, and details on scope (e.g., whether opted-out data is retroactively excluded).

   • [claimed-docs] “You can opt out of model training in Settings.”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Granola
   Granola~partialclaimed5/10

   Docs confirm concrete retention controls: automatic transcript deletion after a set period (transcripts only, notes unaffected) and an opt-out of model training in Settings, giving users some control over data handling. However, there's no evidence of full note/data deletion, account-level data purge, or granular retention policies beyond transcripts. Missing for 10: full note/data deletion controls, account-wide data export-then-delete workflow, and documented retention periods/config options beyond transcripts.

   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time.”
   • [claimed-docs] “Granola allows you to automatically delete transcripts after a set period of time. This applies only to transcripts — your notes are not aff…”
   • [claimed-docs] “You can opt out of model training in Settings.”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 2 · round to Granola
   Granola~partialclaimed5/10

   Granola offers an explicit opt-out of model training in Settings, which is a direct telemetry/data-usage control, but there is no evidence of a broader opt-out for general product usage/analytics telemetry beyond this single toggle. missing for 10: documentation of a general analytics/telemetry opt-out (not just model-training), independent confirmation the opt-out is honored, and any UI/settings detail beyond the one-line mention.

   • [claimed-docs] “You can opt out of model training in Settings.”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

Sharing

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

   weight 1 · round to Fathom
   Granola—none0/10

   Granola's sharing features (copy note link, CSV export, folder sync to CRM) all share the full note/transcript, not a trimmed audio/video soundbite or highlight clip; no evidence anywhere in the docs pack of a clip-cutting or highlight-extraction feature. Missing for 10: any mention of clip/soundbite creation, timestamp-based excerpting, or audio/video snippet sharing.

   • [claimed-docs] “Your notes are never shared with any participants unless you share the link, or add the note to a folder in your team space.”
   • [claimed-docs] “Copy link will copy a unique URL link to the meeting notes, which you can send to others.”
   • [claimed-docs] “The CSV includes the title, note summary, transcript, and other basic details for each note.”
   • [claimed-docs] “This doc walks through how you can export your meeting notes from Granola, including transcripts.”

   proof ↗⚑ flag

   Fathom~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Granola
   Granola~partialclaimed5/10

   Docs confirm private-by-default notes (not shared unless you share a link or add to a team folder) and simple link/folder sharing controls, plus workspace-level API keys for admins, but there is no evidence of granular per-link or per-folder permission settings, workspace-wide sharing policy controls, or an admin dashboard/audit view into what has been shared. Missing for 10: granular link/folder/workspace permission settings, admin visibility/audit log of shared notes, org-wide sharing policy controls.

   • [claimed-docs] “Your notes are never shared with any participants unless you share the link, or add the note to a folder in your team space.”
   • [claimed-docs] “Copy link will copy a unique URL link to the meeting notes, which you can send to others.”
   • [claimed-docs] “You can set up Granola to automatically save any notes that are added to Granola folders to the relevant contacts, companies, or deals on Hu…”
   • [claimed-docs] “Workspace admins on Business and Enterprise plans can also create workspace API keys. These belong to the workspace rather than an individua…”

   proof ↗⚑ flag

   Fathom~partialclaimed4/10

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

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

   proof ↗⚑ flag

Transcription

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

   weight 2 · round to Granola
   Granola~partialclaimed5/10

   Docs explicitly state Granola supports multiple languages for both transcription and generated summaries (granola-docs-11), directly confirming the core claim. However, there is no detail on which languages are supported, no mention of handling mid-meeting language switching, and no independent/hands-on corroboration of multilingual accuracy. missing for 10: list of supported languages, evidence of accurate language-switching handling, independent verification of non-English transcription quality.

   • [claimed-docs] “Granola supports multiple languages for transcription and generated meeting summaries.”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 3 · round to Granola
   Granola~partialclaimed6/10

   Granola's docs confirm a 'Speaker tags' feature that labels transcript segments with participant names rather than generic 'Speaker 1/2' or 'Me/Them' labels, indicating some diarization+name-matching capability. However, there's no detail on how names are resolved (calendar matching, manual tagging, or true voice diarization) and no independent/community evidence validating accuracy of this attribution in multi-speaker calls. Missing for 10: technical explanation of the diarization method, accuracy benchmarks, and hands-on/independent verification of correct name attribution across speakers.

   • [claimed-docs] “Speaker tags show each participant's name above their parts of the conversation, giving you more detailed attribution than the default Me an…”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag

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

   weight 3 · round drawn
   Granola—none0/10

   The evidence pack documents feature-level transcription capabilities (multi-language support, speaker tags, auto-deletion, export) but contains no documentation of the underlying transcription model, accuracy benchmarks, or explicit known limitations (e.g., accent/noise handling, word-error-rate). Community comments raise trust/skepticism but do not confirm or deny transcription documentation quality.

   • [claimed-docs] “Granola supports multiple languages for transcription and generated meeting summaries.”
   • [claimed-docs] “Speaker tags show each participant's name above their parts of the conversation, giving you more detailed attribution than the default Me an…”
   • [claimed-docs] “Works with Zoom, Google Meet, Teams and every other meeting app.”

   proof ↗⚑ flag

   Fathom—none0/10

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

   ⚑ flag