--- schema_version: "1" id: deb1ded0d0b41fa5a8e6cad57f1d4fb0f10ec4f0d2556eca9f9aa43f7824fd5c title: Agent Registration collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/agentic-memory-context/guides/set-up-agentic-memory/agentic-memory-agent-registration.md canonical_url: https://developer.salesforce.com/docs/data/agentic-memory-context/guide/agentic-memory-agent-registration.html source_site: developer.salesforce.com content_type: documentation content_hash: 888625e83ba02e7eeafbee95c1ed44c69558114bdf1586ef015ee38c22a271e7 products: - Agentic Memory & Context - Data 360 Developer Documentation --- # Agent Registration Agent registration is a one-time setup process that provisions the infrastructure your agents need to store conversations, extract memories, and retrieve context. After registration, agents can immediately begin to ingest conversations and provide contextualized responses. You can register agents through the Data 360 UI or the Agentic Memory and Context APIs. ## Register an Agent Using the UI Register an agent to provision the infrastructure it needs to ingest conversations, extract memories, and retrieve context. Data 360 creates the agentic setup for your data space and provisions all infrastructure when you register your first agent. | User Permissions Needed | | | ----------------------- | ----------------------------------- | | To register an agent: | Data Cloud Architect Permission Set | 1. In Data 360, under the **Agent Config** tab, click **New**. 2. In the **Configure Agent** modal, enter these details. | Field | Description | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Agent Name | Human-readable display name for the agent. Data 360 auto-generates the Agent API Name from this value. | | Agent API Name | Developer name used to identify this agent in all API calls. You can't change this value after creation. | | Data Space | The data space that this agent belongs to. Determines which data the agent can access and which Unified Individual DMO it uses. An agent can belong to only one data space. | | Profile DMO | The data model object used for profile unification. This field appears only if your data space has more than one Identity Resolution ruleset. If only one ruleset exists or no Unified Individual DMOs are configured, Data 360 handles this for you. | 3. Click **Save**. Data 360 provisions all infrastructure behind the scenes. The agent enters a Processing status and transitions to Active after everything is ready. > **Note:** You can't use the agent for API calls until it reaches Active status. All Conversation and Context APIs return errors for agents in Processing status. ## Register an Agent Using the API To register an agent programmatically, first create an agentic setup for your data space, then register the agent against that setup. For complete endpoint details, request schemas, and response formats, see [Agent Configuration](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Agent-Configuration). ## What Gets Created Automatically When you register an agent, Data 360 creates these configurations. - Agentic setup for the data space, if this is the first agent in the data space. - Ingestion API connectors and data lake objects (DLOs) to ingest raw conversations, memory, summaries, and execution traces. - Data model objects (DMOs) and mappings to store session-level data (raw conversations, short-term memory, summaries) and profile-level data (long-term memory). - Session data graph to capture session-level information including raw conversation data, short-term memory, and summaries. - Profile data graphs to capture long-term memory and references to sessions. Data 360 creates two out-of-the-box profile data graphs by default: one rooted in Individual and one rooted in User. ## Agent Status After registration, your agent moves through these status states. | Status | Description | | ---------- | ---------------------------------------------------------------------------------------------- | | Processing | Registration in progress. The system is provisioning infrastructure. Agent not yet usable. | | Active | Registration complete. All infrastructure is working normally. Agent ready for full operation. | | Error | Agent facing errors. Check underlying data graphs for error details. | ## Delete an Agent You can delete an agent from the Registered Agents list or via the API. > **Note:** Deleting an agent removes agent-specific data including conversations, session history, and extracted memories associated with this agent. You can't undo this action. ## Considerations - Data 360 derives agent status only from the out-of-the-box data graphs. If an additional real-time data graph is in error or still in creation, the agent remains active. - If an additional real-time data graph is unavailable during context retrieval, Data 360 returns data from out-of-the-box sources only and includes a warning in response metadata. The agent remains fully operational. - The Profile DMO selection applies to the entire data space, not just the agent that you register. All agents in the same data space use the same profile unification logic. This approach keeps the user experience consistent and prevents agent amnesia during handovers between agents. - You can't change the agent API name or data space after you create the agent. ## See Also - [_Salesforce Developer_: Agent Configuration](https://developer.salesforce.com/docs/data/connectapi/references/spec#tag/Agent-Configuration)