Update to assistant

Author: handotdev

api-reference/introduction.mdx

@@ -23,7 +23,7 @@ The Admin API key is used for the majority of the API. It is used to trigger upd
 
 ## Chat API key
 
-The Chat API allows you to embed the AI chat experience grounded in your docs and continually kept up to date into any application of your choosing.
+The Chat API allows you to embed the AI assistant experience grounded in your docs and continually kept up to date into any application of your choosing.
 
 Responses include citations so you can point your users to the right places they need to get help.
 
@@ -34,4 +34,4 @@ Responses include citations so you can point your users to the right places they
 </Note>
 
 Now that you have an API key, check out our [example](https://github.com/mintlify/discovery-api-example) for how to use
-the API for AI chat. You can also see a deployed version of this example at [chat.mintlify.com](https://chat.mintlify.com).
+the API for AI assistant. You can also see a deployed version of this example at [chat.mintlify.com](https://chat.mintlify.com).

discovery-openapi.json

@@ -21,8 +21,8 @@
         "x-mcp": {
           "enabled": true
         },
-        "summary": "Create a chat topic",
-        "description": "Creates a topic to manage message history for a given AI chat conversation",
+        "summary": "Create Assistant Chat Topic",
+        "description": "Creates a topic to manage message history for a given AI assistant conversation",
         "responses": {
           "200": {
             "description": "Topic created successfully",
@@ -48,7 +48,7 @@
         "x-mcp": {
           "enabled": true
         },
-        "summary": "Generate a message completion",
+        "summary": "Create Assistant Chat Message",
         "description": "Generate a completion in response to a user query",
         "requestBody": {
           "required": true,

docs.json

@@ -234,14 +234,14 @@
             ]
           },
           {
-            "group": "Updates",
+            "group": "Admin",
             "pages": [
               "api-reference/update/trigger",
               "api-reference/update/status"
             ]
           },
           {
-            "group": "Chat",
+            "group": "Assistant",
             "pages": [
               "api-reference/chat/create-topic",
               "api-reference/chat/generate-message"

openapi.json

@@ -21,7 +21,7 @@
   "paths": {
     "/project/update/{projectId}": {
       "post": {
-        "summary": "Trigger an update",
+        "summary": "Trigger Update",
         "description": "Trigger an update after updating your OpenAPI document by calling this endpoint in a CI check",
         "parameters": [
           {
@@ -56,7 +56,7 @@
     },
     "/project/update-status/{statusId}": {
       "get": {
-        "summary": "Get the status of an update",
+        "summary": "Get Update Status",
         "description": "Get the status of an update from the status ID",
         "parameters": [
           {

settings/authentication-personalization/authentication-vs-personalization.mdx

@@ -11,11 +11,11 @@ be aware of, from most important to least:
 ### Security Guarantees
 
 Authentication is a fully-fledged private documentation solution. Every aspect of your docs,
-including page content, images, search results, and AI chat features, are completely inaccessible to
+including page content, images, search results, and AI assistant features, are completely inaccessible to
 unauthenticated users.
 
 Personalization, on the other hand, offers no security guarantees for your documentation content.
-All page content, images, search results, and AI chat features can be accessed by the public. Even
+All page content, images, search results, and AI assistant features can be accessed by the public. Even
 if you are using the hidden pages feature of Personalization, a motivated attacker would still
 be able to access the content of a hidden page.
 

settings/authentication-personalization/authentication.mdx

@@ -15,7 +15,7 @@ documentation content by requiring users to authenticate before viewing any cont
 - Documentation page content
 - Images used in documentation pages
 - Search results
-- AI chat interactions
+- AI assistant interactions
 
 You can authenticate users through handshake methods such as:
 

support.mdx

@@ -11,7 +11,7 @@ export function openSearch(e) {
 
 <div onClick={openSearch} style={{ cursor: 'pointer' }}>
   <Card title="Ask our docs" icon="message-circle-question" href="https://mintlify.com/docs" arrow={true}>
-    Ask our AI chat assistant that's been trained on our documentation.
+    Ask our AI assistant that's been trained on our documentation.
   </Card>
 </div>