Update chat feature to chatCompletions and fix Tabs formatting

- Change experimental feature name from 'chat' to 'chatCompletions'
- Fix Tabs component usage to use Tabs.Container and Tabs.Content
- Update all documentation references to use chatCompletions terminology
- Maintain consistent provider configurations across all examples

Author: tpayet

guides/ai/getting_started_with_chat.mdx

@@ -6,10 +6,10 @@ description: Learn how to implement AI-powered conversational search in your app
 
 import { Warning, Note } from '/snippets/notice_tag.mdx'
 
-This guide walks you through implementing Meilisearch's chat feature to create conversational search experiences in your application.
+This guide walks you through implementing Meilisearch's chatCompletions feature to create conversational search experiences in your application.
 
 <Warning>
-The chat feature is experimental and must be enabled before use. See [experimental features](/reference/api/experimental_features) for activation instructions.
+The chatCompletions feature is experimental and must be enabled before use. See [experimental features](/reference/api/experimental_features) for activation instructions.
 </Warning>
 
 ## Prerequisites
@@ -18,30 +18,30 @@ Before starting, ensure you have:
 - Meilisearch instance running (v1.15.1 or later)
 - An API key from an LLM provider (OpenAI, Azure OpenAI, Mistral, Gemini, or access to a vLLM server)
 - At least one index with searchable content
-- The chat experimental feature enabled
+- The chatCompletions experimental feature enabled
 
 ## Quick start
 
-### 1. Enable the chat feature
+### 1. Enable the chatCompletions feature
 
-First, enable the chat experimental feature:
+First, enable the chatCompletions experimental feature:
 
 ```bash
 curl \
   -X PATCH 'http://localhost:7700/experimental-features' \
   -H 'Authorization: Bearer MASTER_KEY' \
   -H 'Content-Type: application/json' \
   --data-binary '{
-    "chat": true
+    "chatCompletions": true
   }'
 ```
 
-### 2. Configure a chat workspace
+### 2. Configure a chatCompletions workspace
 
 Create a workspace with your LLM provider settings. Here are examples for different providers:
 
-<Tabs>
-  <Tab label="OpenAI">
+<Tabs.Container labels={["OpenAI", "Azure OpenAI", "Mistral", "Gemini", "vLLM"]}>
+<Tabs.Content label="OpenAI">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/my-assistant/settings' \
@@ -54,8 +54,8 @@ Create a workspace with your LLM provider settings. Here are examples for differ
         "prompt": "You are a helpful assistant. Answer questions based only on the provided context."
       }'
     ```
-  </Tab>
-  <Tab label="Azure OpenAI">
+</Tabs.Content>
+<Tabs.Content label="Azure OpenAI">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/my-assistant/settings' \
@@ -69,8 +69,8 @@ Create a workspace with your LLM provider settings. Here are examples for differ
         "prompt": "You are a helpful assistant. Answer questions based only on the provided context."
       }'
     ```
-  </Tab>
-  <Tab label="Mistral">
+</Tabs.Content>
+<Tabs.Content label="Mistral">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/my-assistant/settings' \
@@ -83,8 +83,8 @@ Create a workspace with your LLM provider settings. Here are examples for differ
         "prompt": "You are a helpful assistant. Answer questions based only on the provided context."
       }'
     ```
-  </Tab>
-  <Tab label="Gemini">
+</Tabs.Content>
+<Tabs.Content label="Gemini">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/my-assistant/settings' \
@@ -97,8 +97,8 @@ Create a workspace with your LLM provider settings. Here are examples for differ
         "prompt": "You are a helpful assistant. Answer questions based only on the provided context."
       }'
     ```
-  </Tab>
-  <Tab label="vLLM">
+</Tabs.Content>
+<Tabs.Content label="vLLM">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/my-assistant/settings' \
@@ -111,10 +111,10 @@ Create a workspace with your LLM provider settings. Here are examples for differ
         "prompt": "You are a helpful assistant. Answer questions based only on the provided context."
       }'
     ```
-  </Tab>
-</Tabs>
+</Tabs.Content>
+</Tabs.Container>
 
-### 3. Send your first chat request
+### 3. Send your first chatCompletions request
 
 Now you can start a conversation:
 

learn/ai_powered_search/conversational_search_with_chat.mdx

@@ -6,10 +6,10 @@ description: Learn how to implement AI-powered conversational search using Meili
 
 import { Warning } from '/snippets/notice_tag.mdx'
 
-Meilisearch's chat feature enables AI-powered conversational search, allowing users to ask questions in natural language and receive direct answers based on your indexed content. This feature transforms the traditional search experience into an interactive dialogue.
+Meilisearch's chatCompletions feature enables AI-powered conversational search, allowing users to ask questions in natural language and receive direct answers based on your indexed content. This feature transforms the traditional search experience into an interactive dialogue.
 
 <Warning>
-The chat feature is experimental and must be enabled through [experimental features](/reference/api/experimental_features). API specifications may change in future releases.
+The chatCompletions feature is experimental and must be enabled through [experimental features](/reference/api/experimental_features). API specifications may change in future releases.
 </Warning>
 
 ## What is conversational search?
@@ -22,7 +22,7 @@ Conversational search allows users to:
 
 This approach bridges the gap between traditional search and modern AI experiences, making information more accessible and intuitive to find.
 
-## How chat differs from traditional search
+## How chatCompletions differs from traditional search
 
 ### Traditional search workflow
 1. User enters keywords
@@ -37,21 +37,21 @@ This approach bridges the gap between traditional search and modern AI experienc
 
 ## RAG implementation simplified
 
-The chat feature implements a complete Retrieval Augmented Generation (RAG) pipeline in a single API endpoint. Traditional RAG implementations require:
+The chatCompletions feature implements a complete Retrieval Augmented Generation (RAG) pipeline in a single API endpoint. Traditional RAG implementations require:
 
 - Multiple LLM calls for query optimization
 - Separate vector database for semantic search
 - Custom reranking solutions
 - Complex pipeline management
 
-Meilisearch's chat consolidates these into one streamlined process:
+Meilisearch's chatCompletions consolidates these into one streamlined process:
 
 1. **Query understanding**: Automatically transforms questions into optimal search parameters
 2. **Hybrid retrieval**: Combines keyword and semantic search for superior relevance
 3. **Answer generation**: Uses your chosen LLM to generate responses
 4. **Context management**: Maintains conversation history automatically
 
-## When to use chat vs traditional search
+## When to use chatCompletions vs traditional search
 
 ### Use conversational search when:
 - Users need direct answers to specific questions
@@ -67,7 +67,7 @@ Meilisearch's chat consolidates these into one streamlined process:
 
 ## Architecture overview
 
-The chat feature operates through workspaces, which are isolated configurations for different use cases or tenants. Each workspace can:
+The chatCompletions feature operates through workspaces, which are isolated configurations for different use cases or tenants. Each workspace can:
 
 - Use different LLM providers (OpenAI, Azure OpenAI, Mistral, Gemini, vLLM)
 - Apply custom prompts
@@ -93,7 +93,7 @@ The chat feature operates through workspaces, which are isolated configurations
 
 ## Security considerations
 
-The chat feature integrates with Meilisearch's existing security model:
+The chatCompletions feature integrates with Meilisearch's existing security model:
 
 - **API key permissions**: Chat only accesses indexes visible to the provided API key
 - **Tenant tokens**: Support for multi-tenant applications
@@ -102,6 +102,6 @@ The chat feature integrates with Meilisearch's existing security model:
 
 ## Next steps
 
-- [Get started with chat implementation](/guides/ai/getting_started_with_chat)
-- [Explore the chat API reference](/reference/api/chats)
+- [Get started with chatCompletions implementation](/guides/ai/getting_started_with_chat)
+- [Explore the chatCompletions API reference](/reference/api/chats)
 - [Learn about experimental features](/reference/api/experimental_features)

reference/api/chats.mdx

@@ -10,10 +10,10 @@ import { Warning } from '/snippets/notice_tag.mdx'
 The `/chats` route enables AI-powered conversational search by integrating Large Language Models (LLMs) with your Meilisearch data. This feature allows users to ask questions in natural language and receive contextual answers based on your indexed content.
 
 <Warning>
-The chat feature is experimental and must be enabled through [experimental features](/reference/api/experimental_features). To enable it, set `"chat": true` in your experimental features configuration.
+The chatCompletions feature is experimental and must be enabled through [experimental features](/reference/api/experimental_features). To enable it, set `"chatCompletions": true` in your experimental features configuration.
 </Warning>
 
-## Chat workspace object
+## ChatCompletions workspace object
 
 ```json
 {
@@ -25,11 +25,11 @@ The chat feature is experimental and must be enabled through [experimental featu
 
 | Name             | Type   | Description                                                                                     |
 | :--------------- | :----- | :---------------------------------------------------------------------------------------------- |
-| **`workspace`**  | String | Unique identifier for the chat workspace                                                       |
+| **`workspace`**  | String | Unique identifier for the chatCompletions workspace                                                       |
 | **`createdAt`**  | String | Creation date of the workspace, represented in [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format |
 | **`updatedAt`**  | String | Latest update date of the workspace, represented in [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format |
 
-## Chat settings object
+## ChatCompletions settings object
 
 ```json
 {
@@ -111,8 +111,8 @@ data: [DONE]
 
 ### Example
 
-<Tabs>
-  <Tab label="cURL">
+<Tabs.Container labels={["OpenAI", "Azure OpenAI", "Mistral", "Gemini", "vLLM"]}>
+<Tabs.Content label="cURL">
     ```bash
     curl \
       -X POST 'http://localhost:7700/chats/customer-support/chat/completions' \
@@ -129,8 +129,8 @@ data: [DONE]
         "stream": true
       }'
     ```
-  </Tab>
-  <Tab label="JavaScript">
+</Tabs.Content>
+<Tabs.Content label="JavaScript">
     ```javascript
     const response = await fetch('http://localhost:7700/chats/customer-support/chat/completions', {
       method: 'POST',
@@ -161,8 +161,8 @@ data: [DONE]
       console.log(chunk);
     }
     ```
-  </Tab>
-</Tabs>
+</Tabs.Content>
+</Tabs.Container>
 
 ## Update chat settings
 
@@ -195,8 +195,8 @@ Returns the updated settings object. Note that `apiKey` is write-only and will n
 
 ### Examples
 
-<Tabs>
-  <Tab label="OpenAI">
+<Tabs.Container labels={["OpenAI", "Azure OpenAI", "Mistral", "Gemini", "vLLM"]}>
+<Tabs.Content label="OpenAI">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/customer-support/settings' \
@@ -209,8 +209,8 @@ Returns the updated settings object. Note that `apiKey` is write-only and will n
         "prompt": "You are a helpful customer support assistant."
       }'
     ```
-  </Tab>
-  <Tab label="Azure OpenAI">
+</Tabs.Content>
+<Tabs.Content label="Azure OpenAI">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/customer-support/settings' \
@@ -224,8 +224,8 @@ Returns the updated settings object. Note that `apiKey` is write-only and will n
         "prompt": "You are a helpful customer support assistant."
       }'
     ```
-  </Tab>
-  <Tab label="Mistral">
+</Tabs.Content>
+<Tabs.Content label="Mistral">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/customer-support/settings' \
@@ -238,8 +238,8 @@ Returns the updated settings object. Note that `apiKey` is write-only and will n
         "prompt": "You are a helpful customer support assistant."
       }'
     ```
-  </Tab>
-  <Tab label="Gemini">
+</Tabs.Content>
+<Tabs.Content label="Gemini">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/customer-support/settings' \
@@ -252,8 +252,8 @@ Returns the updated settings object. Note that `apiKey` is write-only and will n
         "prompt": "You are a helpful customer support assistant."
       }'
     ```
-  </Tab>
-  <Tab label="vLLM">
+</Tabs.Content>
+<Tabs.Content label="vLLM">
     ```bash
     curl \
       -X PUT 'http://localhost:7700/chats/customer-support/settings' \
@@ -266,8 +266,8 @@ Returns the updated settings object. Note that `apiKey` is write-only and will n
         "prompt": "You are a helpful customer support assistant."
       }'
     ```
-  </Tab>
-</Tabs>
+</Tabs.Content>
+</Tabs.Container>
 
 ## Get chat settings
 
@@ -295,15 +295,15 @@ Returns the settings object without the `apiKey` field.
 
 ### Example
 
-<Tabs>
-  <Tab label="cURL">
+<Tabs.Container labels={["OpenAI", "Azure OpenAI", "Mistral", "Gemini", "vLLM"]}>
+<Tabs.Content label="cURL">
     ```bash
     curl \
       -X GET 'http://localhost:7700/chats/customer-support/settings' \
       -H 'Authorization: Bearer MASTER_KEY'
     ```
-  </Tab>
-</Tabs>
+</Tabs.Content>
+</Tabs.Container>
 
 ## List chat workspaces
 
@@ -329,15 +329,15 @@ List all available chat workspaces. Results can be paginated using query paramet
 
 ### Example
 
-<Tabs>
-  <Tab label="cURL">
+<Tabs.Container labels={["OpenAI", "Azure OpenAI", "Mistral", "Gemini", "vLLM"]}>
+<Tabs.Content label="cURL">
     ```bash
     curl \
       -X GET 'http://localhost:7700/chats?limit=10' \
       -H 'Authorization: Bearer MASTER_KEY'
     ```
-  </Tab>
-</Tabs>
+</Tabs.Content>
+</Tabs.Container>
 
 #### Response: `200 OK`
 

reference/api/experimental_features.mdx

@@ -26,7 +26,7 @@ The experimental API route is not compatible with all experimental features. Con
   "containsFilter": false,
   "editDocumentsByFunction": false,
   "network": false,
-  "chat": false
+  "chatCompletions": false
 }
 ```
 
@@ -37,7 +37,7 @@ The experimental API route is not compatible with all experimental features. Con
 | **`containsFilter`**          | Boolean | `true` if feature is active, `false` otherwise |
 | **`editDocumentsByFunction`** | Boolean | `true` if feature is active, `false` otherwise |
 | **`network`**                 | Boolean | `true` if feature is active, `false` otherwise |
-| **`chat`**                    | Boolean | `true` if feature is active, `false` otherwise |
+| **`chatCompletions`**         | Boolean | `true` if feature is active, `false` otherwise |
 
 ## Get all experimental features
 
@@ -58,7 +58,7 @@ Get a list of all experimental features that can be activated via the `/experime
   "containsFilter": false,
   "editDocumentsByFunction": false,
   "network": false,
-  "chat": false
+  "chatCompletions": false
 }
 ```
 
@@ -87,6 +87,6 @@ Setting a field to `null` leaves its value unchanged.
   "containsFilter": false,
   "editDocumentsByFunction": false,
   "network": false,
-  "chat": false
+  "chatCompletions": false
 }
 ```