---
title: Registering an agent
slug: registering-an-agent
docTags: 
createdAt: 2026-08-25T21:33:37.788Z
---

Agent registration captures an agent’s metadata and intent. Registration requirements and available actions depend on whether the agent belongs to the Global Agent Registry or the Account Agent Registry. 

For account agents, registration captures the agent’s metadata and references the resources it uses, such as the LLM configuration, knowledge base, MCP servers and connectors. Credentials and environment-specific runtime settings are defined later during deployment. Global agents use governed metadata and do not belong to an account context. 

# Interaction modes

You can choose to integrate agents that are native to the platform or use external ones. It also helps you manage, govern and clearly find and execute your agents.

- Define the interaction model of the agent: 
  - Conversational Agents: Designed for user interaction via prompts/questions 
  - Non‑Conversational Agents: Created for background workflows, automation, or API-triggered execution; this is not directly accessible to end users in conversational interfaces.
- Define where the agent executes: 
  - Bridge-hosted agents 
  - External-hosted agents (executed via external APIs like WatsonX or others)

# Registering an agent from an existing repository  

Use** File Upload** to register multiple accounts or global agents from an existing repository. Follow the steps below to begin the registration: 

1. From the main menu, go to **Services** → **Platform Services** → **Agent Library**. 
2. Decide whether the agents belong in the **Account Agent Registry** or the **Global Agent Registry**. This choice determines which manifest fields you must complete.
3. Locate  the *manifest.json* file within your repository. This file typically contains essential metadata and configuration details for the agent you wish to import.  

:::Paragraph{indent="1"}
Source: GitHub kyndryl-agentic-ai org → bdg-sw-agents--base repo → config/ directory 
:::

4. Review the file and update account-specific fields. The required manifest fields depend on the selected registry type: 

For Account Agent Registry, review and update the account-specific fields listed below.  

:::Paragraph{listStyleType="disc" indent="2"}
tenant\_id — the account's Bridge tenant ID
:::

:::Paragraph{listStyleType="disc" indent="2"}
connection\_ids — map to the connections created
:::

:::Paragraph{listStyleType="disc" indent="2"}
access\_group\_id — map to the access group
:::

:::Paragraph{listStyleType="disc" indent="2"}
service\_id — map to the Service ID
:::

:::Paragraph{listStyleType="disc" indent="2"}
knowledge\_base\_id — map to the knowledge base (if applicable)
:::

:::Paragraph{listStyleType="disc" indent="2"}
llm\_api\_key\_id — map to the API key
:::

For Global Agent Registry, account-specific fields such as tenant\_id, connection\_ids, access\_group\_id and llm\_api\_key\_id do not apply. Provide the mandatory global metadata instead.

5. Once the information is correct, go to the **Agent Library** page, and select **Register, **then select Account **Agent Registry** or **Global Agent Registry**, based on the type of agent you need to register.
6. Select the **File Upload **option.
7. Select the *manifest.json* file from your local system.
8. Click **Upload**.

After uploading, the system will process the file, extracting the necessary information to integrate the agent into the library seamlessly. 

# Manual registration

Single registration is the manual process to register an agent. Follow the path below to proceed with the registration: 

1. From the **Agent Library** page, select **Register.**
2. Select Account **Agent Registry** or **Global Agent Registry**, based on the type of agent you need to register.  
3. Select **Single Registration. **Select the Account Agent Registry or Global Agent Registry option based on where the agent will be managed.  

Provide the following details for the registration: 

::::WorkflowBlock
:::WorkflowBlockItem
### Basic information

- **Type**: Select **Agent** or **Agentic Solution**
- **Name**: Enter a unique name for the agent
- **Version**: Enter the version number
- **Description**: Add a short description 
- **Owner**: Enter the agent owner
- **Maintaining Team**: Enter the team responsible for updates
- **Tags**: Add tags separated by a comma.
- **Technology Framework**: Select the framework used
- **Summary**: Enter a summary of the agent’s purpose.

For Global Agent Registry, provide the mandatory global metadata, including: 

- Name 
- Description 
- Agent type 
- Owner 
- Governance metadata 
- Supported configuration schema.  
:::

:::WorkflowBlockItem
### Skills

- **Skill Name**: Enter a unique skill name.
- **Skill Description**: Add a short description.

Select **Add Skill** to add more or **Next** to continue.
:::

:::WorkflowBlockItem
### Configurations

The configurations section applies to the Account Agents. Global Agents use a supported configuration schema and do not include account-specific runtime configuration.

- **LLM**
  - Configuration: Select LLM configuration
  - LLM Model: Select model
- **Knowledge Base**
  - Configuration: Select Global or Private
  - Knowledge Base: Select a knowledge base
- **MCP**
  - MCP Server: Select MCP server
  - MCP Tool: Select MCP tool
- **Connector**
  - Type: Select connector type

Select **Next** to continue.
:::

:::WorkflowBlockItem
### Schema

- Enter input and output schema
- Or select **Default**

Select **Next** to continue
:::

:::WorkflowBlockItem
### Source of agent

- **GitHub Repository URL**: Enter GitHub repository URL
- **Branch**: Enter repository branch
- **Manifest Path**: Enter manifest path.

Select **Next** to continue.
:::

:::WorkflowBlockItem
### Flow configuration

Agentic Solution only

- Enter JSON or YAML flow.

Select **Next** to continue.
:::

:::WorkflowBlockItem
### Review and submit

Review all information and select **Submit**.** **
:::
::::

#