Enable For Agents

Enabling a graph for Agents makes it discoverable in the Agent tooling list, allowing it to be selected as a tool during Agent creation. Once selected, the Agent uses the graph’s description and input schema at runtime to determine whether to invoke the graph and what data to provide.

Prerequisites

• API Listener: The graph must include a valid API Listener. Only API Listener–based graphs can be enabled and used as Agent tools.

• Graph Scope: The graph must belong to the same organization and project as the Agent.

• Deployment Readiness: While deployment status does not block enablement, Agents execute deployed graph versions at runtime.

• Permissions: You must have permission to enable or disable graphs for Agent use.

Click on the Enable for Agents button. The Enable for Agents window appears, providing context and capturing all required information for Agent execution. These fields are captured on enable. To update them, disable and enable them again.

• Deployment Status by Environment: Agents can only call graphs that are deployed and running.

  Displays the selected Graph name, current deployment status, and lists available environments (For Example, Production, Pre-Production, Non-Production)

• Graph Description: Describe what this graph does so Agents can decide whether to use it at runtime.

• Graph Input: Describe the input this graph expects so Agents know how to provide it at runtime (JSON format). JSON input is validated using the existing JSON validation library. Format errors are surfaced with clear error messages before enablement can proceed.

 Graph Description and Input details are captured during enablement. To update them later, the graph must be disabled and enabled again.

• Cancel: Click Cancel to close the window without saving changes.

• Enable for Agents:  Becomes active only when all required fields are completed. Click the Enable for Agents button to trigger system validation and enable the graph for Agent use.

After a graph is successfully enabled, a confirmation modal appears summarising the configured details:

• Graph name

• Graph Description

• Graph Input

• Enabled by (Publisher)

• Description and input fields are truncated to a single line by default. Selecting this field expands it to display the full content.

• The modal height adjusts automatically to accommodate expanded content. Also, selecting the field again collapses it back to the truncated view. Click Done to close the successful confirmation window.

Switching the top‑bar action from Enable for Agents to Hide from Agents immediately updates the tag, without requiring a page reload. Enabled for Agents tag indicates that a graph is currently available for use by AI Agents.

Disabled for versions

Publishing a graph as an Agent tool is disabled when viewing a published (locked) version. Version mode is read‑only, and all publish or unpublish actions must be performed from the Current version to avoid modifying the visibility of a historical snapshot.

When a published version is active, the editor is greyed out, graph edits are disabled, and actions such as Enable for Agents or Hide from Agents are unavailable. You can still see whether the graph is currently exposed as a tool, but you cannot change that state.

Attempting to hide or enable the graph in a previous version has no effect, and you are prompted to switch back to the Current version to make changes.

Removing Listener

When a graph enabled for Agents has its API Listener, you are warned while removing the listener that this action will prevent the graph from being available as an Agent tool.

• Selecting Remove Listener from the Graph Options dropdown opens a confirmation window explaining the impact.

The graph will be hidden from Agent tool selection, preventing new Agent configurations from using it. After redeployment, any Agent calls to this graph will fail if they depend on the listener. Removing the listener also deletes any associated default metrics. If you want to retain metrics are advised to edit and update the listener type instead.

• You must acknowledge a confirmation checkbox indicating they understand the risk of Agent errors before proceeding. Once completed, a success message confirms that the listener was removed and the graph is hidden from Agent tool selection, while existing deployments remain unaffected until redeployment.

• Click Done to close the window.

Editing Listener

When the listener type is changed on a graph currently enabled for Agents, the system warns you that this action will remove the existing API Listener and prevent the graph from being available as an Agent tool.

• Select Edit Listener from the Graph Options dropdown to open the Listener Editor.

• Change the listener type as required (For Example, from API to Queue), and click Save Edits to save the changes, which triggers a warning window explaining the impact. Confirming the change hides the graph from Agent tool selection, preventing new Agent configurations from using it.

It informs you that after redeployment, any Agent calls to this graph will fail if an Agent depends on it, though there is no runtime impact until redeployment.

• Select the check box to confirm that dependencies have been reviewed before proceeding.

• Click Save Edit to save the changes. The API Listener is removed, and any previously configured Agent enablement details for the graph are cleared, with a success message confirming that the graph is no longer available for Agent use.

Deleting Graph

Graph Version Restoration