Tools

Tools are the actions an agent can take to interact with the world, such as calling an API, searching the web, running code, querying a database, or sending a message. They extend the agent’s abilities beyond just thinking and talking.

Xponent Graphs

In this step, you choose which Xponent Graphs the agent can use as callable tools. If no Xponent Graphs are available for agent use, the right‑hand section displays the message “No Xponent Graphs available. Publish Graphs for Agent use in your organization.”

Just below the Xponent Graphs section, the UI displays how many tools are available, for example: 02 tools available. This indicates the maximum number of Xponent Graphs that can be selected as tools for the agent.

Once graphs are available, you can select Xponent Graphs from your projects to allow the agent to invoke them as tools. Start by selecting an environment. The available environments are:

• Production

• Pre‑Production

• Non‑Production

After selecting an environment, the list of graphs deployed in that environment is displayed along with their deployment status.

• Graphs can be searched using the search (Find) box. You can select multiple graphs within the same environment.

• If you change the selected environment, any previously selected graphs are cleared.

• For Non‑Production environments, an additional Environment column is displayed to indicate whether the graph belongs to QA, Development, or another environment.

• Once a graph is selected, graph names appear in the left‑hand panel along with the environment they are associated with. This allows you to review which graphs the agent can access before continuing.

API Tools

The API Tools feature allows your agent to call external APIs during execution. This enables the agent to retrieve data from external systems or trigger actions in downstream services, depending on the API's capabilities. In the setup panel, you define the API endpoint, authentication, and request details so the agent can call the API consistently and safely.

API Tools Selection

The available API tools are displayed in the right-hand section of the page. Select the required API tool to add it to the agent configuration. Once selected, the tool is added to the left-hand panel under the list of selected tools.

You can remove a selected API tool in either of the following ways:

• Select the X icon next to the tool in the selected tools list.

• Clear the tool selection from the API tools list.

When a tool is selected, it appears in the left-hand panel, confirming that it has been added to the agent configuration.

The API tools list provides additional options to help manage and locate tools:

• Use the Find (search) box to search for specific API tools.

• Sort the list in ascending or descending order by selecting the Tool Name column heading.

• Select the View (👁️) icon to preview an API tool's configuration details. To close the preview, select the Back (⬅️) icon.

• If an API tool is currently used by one or more agents, a usage indicator is displayed next to the tool name, for example, Used by 1 agent. This helps identify tools that are already associated with existing agent configurations. If the tool is not being used by any agent, no usage indicator is displayed.

To create a new API tool, select Add Tool located in the bottom-right corner of the API tools list and provide the endpoint details you want the agent to call. Each tool represents one API configuration that the agent can later select and use.

Tool Details

• Name: Enter a clear, descriptive name that makes it easy to recognize the purpose of the tool. For example, use a name that reflects the outcome, such as Get Customer Profile or Create Support Ticket, rather than a generic name like API 1.

• Description: Add a short explanation of what the API does and when the agent should use it. A good description helps other configurators understand the intent and reduces misuse. For example, you can mention what the API returns or what action it performs.

• URL: Enter the complete API endpoint URL. This should include the base path and resource path required by the API. If the endpoint requires dynamic values (such as an ID), you can use variables in the URL (see Variables section below).

Request Method

Select the HTTP method the agent should use when calling the API. The supported methods include:

• GET - Retrieve information (read-only requests).

• POST - Create or submit information (commonly used when sending a body).

• PUT - Replace an existing resource.

• PATCH - Update part of an existing resource.

• DELETE - Remove a resource.

Choosing the correct method is important because many APIs validate the method and may reject requests that do not match the expected operation.

Request Configuration

• Headers (JSON): Use headers to provide additional request metadata, such as content type, accepted response format, correlation IDs, or API keys (when applicable). Headers must be provided in JSON format.

• Params: Use params (query parameters) to pass values in the URL query string. This is common for filters, pagination, or search inputs. If your UI expects params as key/value pairs, add them accordingly. If it expects JSON, use a JSON structure similar to headers.

• Request Body (JSON): Use the request body to send data for methods such as POST, PUT, or PATCH. The body must be in JSON

Authentication

Authentication determines how the agent proves it is allowed to call the endpoint. Select the authentication type that matches the API requirements:

• None: Use this only when the endpoint does not require authentication.

• Basic Auth: Use Basic Auth when the API requires a username and password. Provide:

  • Username

  • Password

• API Key: Use API Key authentication when the API expects a key passed in a header. Provide:

  • Header Name (for example, x-api-key or Authorization)

  • API Key Value

Variables

Variables allow you to insert dynamic values into the tool configuration so the agent can call the same API with different values at runtime. You can use variables in the URL, params, headers, or request body, depending on the supported fields.

Generic Tools

In addition to Xponent Graphs and API tools, you can enhance an agent’s capabilities by adding Generic Tools. Generic tools provide built‑in functionality that agents can use without additional configuration.

To add a generic tool:

• Select the Add a tool option.

• A list of available generic tools is displayed.

• Select the tool you want to add. For example, select Web Search.

The Web Search tool allows the agent to search publicly available information on the web to support its reasoning or decision‑making. This is useful when the agent needs additional context or up‑to‑date information that is not part of its configured knowledge base.

Once selected, the Web Search tool is added to the agent’s tool list.

Review Selected Tools

All selected tools, including generic tools, appear in the left‑hand panel, allowing you to review which tools the agent has access to before completing the setup.

After selecting the required tools:

• Review the agent configuration to ensure all required steps are complete.

• Select Create Agent to complete the agent creation.