UnieAI Studio

From Creating a CM to Using It in Chat

Choose a model, prepare knowledge and tools, connect them to a Customize Model, validate it in Playground, and deliver it to Chat.

This guide walks you through creating a working CM (Customize Model) from start to finish. You will prepare the data and tools it needs, connect them to the CM, test the result, and make the CM available in Chat.

Knowledge bases, SQL databases, API Tools, and MCP are optional. Create only the capabilities your CM needs. For general conversation, you can proceed directly from model selection and CM creation to Playground testing and Chat setup.

What You Will Complete

  • A CM with a selected base model
  • Documents, data, or external tools the CM can use
  • A set of tests validated in Playground
  • A model that users can select in Chat

Before You Start

  • Switch to the intended personal space or organization workspace.
  • Confirm that you can create a CM and the required assets.
  • Prepare the documents, data, and services you want to connect.
  • If the CM will be delivered to Chat, confirm that you can manage the appropriate Chat Provider.

Assets are created in the currently selected workspace. Check the workspace first so the intended users can access them later.

Complete Workflow

Choose a Base Model and Create the CM

UnieAI Model Zoo, where you choose the CM's base model.

Confirm the model name and intended use here before adopting it and creating the CM.

  1. In the sidebar, go to Marketplace → UnieAI Model Zoo.
  2. Choose a suitable model, then select Use Base Model → Add to My Models.
  3. Go to My Assets → My Models and select Create Customize Model.
  4. Select the base model you just added, enter a CM name, and complete creation.

Use a text model for general text conversations. If the CM must read images or document images, choose a model that supports that content. After creation, the CM overview opens.

Create a Knowledge Base

Create knowledge base dialog for entering its name and description.

The name and description make the knowledge base easy to identify later in the CM data-source list.

  1. Go to My Assets → My Knowledge Bases and select New Knowledge Base.
  2. Enter a clear name and purpose, then create it.
  3. Add the documents the CM should reference.
  4. Wait until document processing is complete.
  5. Use Search in the knowledge base to confirm that the correct content can be found.

Search with questions your actual users are likely to ask. If important content cannot be found, revise the documents before continuing.

Create a SQL Database

The connection-information step for adding a SQL database.

Complete the guided steps and confirm that the connection test succeeds before assigning the database to the CM.

  1. Go to My Assets → My SQL Databases.
  2. Select Add Data → Database.
  3. Complete the connection information, account permissions, and access scope shown on screen.
  4. Select Test Connection. Complete creation only after the test succeeds.
  5. Confirm that the database has been added and is available in the CM selection list.

For production data, start with read-only access and expose only the data required for the CM's task.

Create an API Tool

My API Tools, where reusable API tools are created and managed.

A completed tool appears here and can then be selected from the CM's feature settings.

  1. Go to My Assets → My API Tools.
  2. Select Add API Tool.
  3. Enter a name and clearly state when the tool should be used.
  4. Complete the service location, required data, and authorization settings shown on screen.
  5. Save the tool and confirm that it is enabled.

Keep each tool focused on one clear task, such as checking an order status or creating a support case.

Create an MCP Connection

My Remote MCP page for creating and managing MCP connections.

Confirm that the MCP connection lists its tools here before adding it to the CM.

  1. Go to My Assets → My Remote MCP.
  2. Select Add MCP Server.
  3. Complete the server, authorization, tools, and sharing steps.
  4. If Sign in and authorize appears, finish sign-in and return to Studio.
  5. Confirm that the status is normal and that the required tools appear in the list.

Resolve a Sign-in required or Disabled status before connecting the MCP server to the CM.

Connect Data and Tools to the CM

The CM Data Sources page showing connected knowledge bases and SQL databases.

Manage knowledge bases and SQL databases on Data Sources, and add API tools and MCP connections from their corresponding feature pages.

Return to the CM and complete the applicable settings:

CapabilityLocation in the CMAction
Knowledge baseData → Knowledge BaseSelect the knowledge bases the CM can search
SQL databaseData → SQL DatabaseSelect the databases the CM can query
API ToolBehavior → API ToolsEnable the feature and select the tools
MCPBehavior → MCPEnable the feature and select the MCP servers

Confirm that each selection has been saved. Then go to Behavior → Kernel Prompt and describe the CM's role, response rules, permitted data, and what it should do when information is uncertain.

Creating an asset does not connect it automatically. Each knowledge base, database, and tool must be selected in the target CM.

Test in Playground

Playground with the selected CM and a conversation area for validation.

Before sending a test question, confirm that the model selector shows the CM created in this workflow.

  1. On the CM page, select Try in Playground.
  2. Confirm that the newly created CM is selected at the top.
  3. Test general responses, the knowledge base, SQL, API Tools, and MCP as applicable.
  4. Check that answers are correct, use the expected data, and avoid actions that should not be performed.
  5. After changing the CM, start a new conversation and test again.
Test typeExample
GeneralWhat can you help me with?
DocumentsAccording to company policy, how early must leave be requested?
DataSummarize this month's order count by region.
ToolCheck the current status of order 12345.
Missing informationAsk for an order lookup without providing an order number.
Permission boundaryRequest unauthorized data or an unavailable action.

Continue to Chat setup only after all planned capabilities pass testing.

Prepare for Chat Delivery

API Keys page for creating and copying the key used by the Chat Provider.

Copy the key directly into Chat when it is shown. Do not place it in documentation or screenshots.

  1. Go to API Keys.
  2. Find the API Key for Chat and select Copy Secret. If no suitable key exists, select Create Key, finish creating it, and then copy it.
  3. Return to the CM and go to Operations → Integrate to obtain the information and CM identifier needed for Chat.
  4. Confirm that the CM, base model, and required assets are available.

Copy the API Key from the API Keys page, not from the CM integration page. Store it securely and do not place it in public documents, group messages, or screenshots.

Add and Select the CM in Chat

Chat account menu with access to private settings and the administrator toolbox.

Open Account & Privacy Settings for a private Provider. Administrators use Administrator Toolbox for global Provider settings.

Choose one Provider type based on who should use the CM:

Provider typeUse caseWho can use it
Private ProviderPersonal use or initial testingThe creator only
Group ProviderShared use by a specific teamMembers of that group
Global ProviderShared across the Chat platformAll platform users

All three Provider forms require the following information:

FieldRequiredWhat to enter
Display NameYesA recognizable Chat name, such as “Company Support CM”
PrefixYesFour letters or numbers that are not already used by another Provider, such as CM01
API URLYesThe Base URL shown under Operations → Integrate in the Studio CM
API KeyYesThe API Key copied from Studio API Keys

In Chat, enter Studio's Base URL in the API URL or API Endpoint field. Do not enter the separate “Endpoint” value or add anything else. Paste the API Key in full without leading or trailing spaces.

Private Provider

Private Providers page before a Provider is added.

Use Add Provider in the upper-right corner to begin.

  1. Open Account & Privacy Settings from the account menu.
  2. Open the Private Providers tab and select Add Provider.
  3. Enter the CM name in Display Name.
  4. Enter four letters or numbers in Prefix. Choose another value if the Prefix already exists.
  5. Paste the Studio Base URL into API URL.
  6. Paste the API Key copied from Studio into API Key.
  7. Confirm all four fields and select Create Provider.

Private Provider creation form with the required fields.

Complete all four fields. Keep the API Key masked whenever the screen is shared or captured.

Private Provider with synchronized models ready for selection.

After creation, synchronize the models, select the CM that should be available, and save the selection.

If Private Providers is not visible, ask a group editor to create a Group Provider or an administrator to create a Global Provider.

Group Provider

Group Provider settings page before a Provider is added.

The add button is available to the group Creator and Editors who can manage Provider settings.

  1. Open My Groups and select the group that will use the CM.
  2. Open Provider Settings and find Group Providers.
  3. Select Add Provider.
  4. Enter a recognizable CM name in Display Name.
  5. Enter a unique four-character alphanumeric Prefix.
  6. Paste the Studio Base URL into API URL.
  7. Paste the API Key copied from Studio into API Key.
  8. Confirm all four fields and select Create Provider.

Group Provider creation form with the required fields.

Complete all four fields and use a Prefix that is not already assigned to another Provider.

Group Provider with synchronized models ready for selection.

Select only the CM models the group should use, then save the selection.

Only the group Creator or Editor can manage Providers. Other group members can use enabled Group Providers but cannot add or change them.

Global Provider

Administrator Toolbox menu with access to Core System Settings.

Open Core System Settings from the Administrator Toolbox, then go to Global Providers.

Global Providers page before a Provider is added.

Select the button in the upper-right corner to open the creation form.

  1. A Chat administrator opens System Settings from the account menu.
  2. Open Global Providers and select Global Provider in the upper-right corner.
  3. Enter a recognizable CM name in Display Name.
  4. Enter a unique four-character alphanumeric Prefix.
  5. Paste the Studio Base URL into API Endpoint.
  6. Paste the API Key copied from Studio into API Key.
  7. Confirm all four fields and select Create Global Provider.

Global Provider creation form with the required fields.

Enter Studio's Base URL in API Endpoint, then complete the remaining required fields.

Global Provider with synchronized models ready for selection.

Synchronize the models, select the CM, and save. The saved selection is available platform-wide when the Provider is enabled.

Only Chat administrators can create and manage Global Providers. An enabled Global Provider is available to all Chat users.

Sync and Verify the CM

  1. Find the new Provider and expand its settings.
  2. Select Sync Models and wait for the completion message.
  3. Search for the CM and select it. Avoid Select All unless every listed model should be available.
  4. Select Save and confirm that the saved message appears.
  5. Confirm that the Provider is enabled. Turn it on if it is marked Disabled.
  6. Start a new Chat conversation and choose the CM from the model selector.
  7. Ask a question that already passed in Playground and confirm the result.

Pre-launch Checklist

  • The correct CM name appears in the Chat model selector
  • General responses match the Playground result
  • Knowledge-base questions use the correct content
  • SQL questions access only permitted data
  • API Tools and MCP run only when appropriate
  • The CM asks for clarification when required information is missing
  • Unauthorized users cannot access restricted assets
  • The API Key is stored by the designated person and does not appear in documents or screenshots

Common Issues