# How to connect Arize AX to Hermes Agent (paste one key, 24 tools) > Connect Arize AX to Hermes with ClawLink: paste your Arize AX key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/arize-ax Most guides for giving Hermes Agent Arize AX access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Arize AX setup: pair once in the browser and your always-on Hermes agent can act on Arize AX for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Arize AX. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Arize AX** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect arize-ax # connect Arize AX (browser OAuth) npx -y @useclawlink/cli actions arize-ax # list available actions npx -y @useclawlink/cli run arize-ax --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Arize AX in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Arize AX API key once. Verify the connection by asking Hermes: > Pull the relevant data from Arize AX, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Arize AX is connected in the dashboard, that agent calls the same 24 Arize AX tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Arize AX MCP for Hermes Looking for a Arize AX MCP server for Hermes Agent? ClawLink connects Arize AX to Hermes Agent and exposes 24 Arize AX tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Arize AX integration](https://claw-link.dev/openclaw/arize-ax) works the same way. ## What the Hermes Agent Arize AX integration can do 24 Arize AX tools are ready for Hermes Agent once the account is connected. ### All 24 Arize AX tools for Hermes | Tool | What it does | |---|---| | **Get dataset** `arize_ax_get_dataset` | Get one Arize dataset and its versions by dataset ID | | **Get experiment** `arize_ax_get_experiment` | Get one Arize experiment by its ID, without its experiment runs | | **Get project** `arize_ax_get_project` | Get one accessible Arize project by its ID | | **Get prompt** `arize_ax_get_prompt` | Get an Arize prompt with its current, explicitly selected, or labeled version | | **Get space** `arize_ax_get_space` | Get one accessible Arize space by its ID | | **List dataset examples** `arize_ax_list_dataset_examples` | List one page of examples from an Arize dataset or a specific dataset version, preserving | | **List datasets** `arize_ax_list_datasets` | List one page of Arize datasets, optionally filtered by space or dataset name | | **List experiment runs** `arize_ax_list_experiment_runs` | List one page of runs and outputs for an Arize experiment, preserving additional run fields | | **List experiments** `arize_ax_list_experiments` | List one page of Arize experiments, optionally filtered by dataset, space, or name | | **List projects** `arize_ax_list_projects` | List one page of accessible Arize projects, optionally filtered by space or project name | | **List prompt versions** `arize_ax_list_prompt_versions` | List one page of versions for an Arize prompt, newest first | | **List prompts** `arize_ax_list_prompts` | List one page of Arize prompts, optionally filtered by space or prompt name | | **List spaces** `arize_ax_list_spaces` | List one page of Arize spaces accessible to the connected API key, optionally filtered by | | **List spans** `arize_ax_list_spans` | Read one bounded page of spans for an Arize project using optional time and filter constraints | | **List traces** `arize_ax_list_traces` | Read one bounded page of traces and nested spans for an Arize project using optional time and | | **Add dataset examples** `arize_ax_add_dataset_examples` | Append arbitrary-field examples to an Arize dataset or a specified dataset version | | **Add experiment runs** `arize_ax_add_experiment_runs` | Append one or more runs to an existing Arize experiment | | **Create dataset** `arize_ax_create_dataset` | Create an Arize dataset in a space with an explicit initial array of examples | | **Create experiment** `arize_ax_create_experiment` | Create an Arize experiment with initial runs, associated with exactly one dataset or space | | **Create prompt** `arize_ax_create_prompt` | Create an Arize prompt and its initial version in a space | | **Create prompt version** `arize_ax_create_prompt_version` | Create a new immutable version of an existing Arize prompt | | **Update dataset** `arize_ax_update_dataset` | Rename an existing Arize dataset | | **Update dataset examples** `arize_ax_update_dataset_examples` | Update existing Arize dataset examples by ID, optionally creating a named dataset version | | **Update prompt** `arize_ax_update_prompt` | Update or clear an Arize prompt's description | ## Example prompts **Get Dataset** > Pull the relevant data from Arize AX, summarize it in plain English, and point out anything that needs attention. **Get Experiment** > Pull the relevant data from Arize AX, summarize it in plain English, and point out anything that needs attention. **Get Project** > Pull the relevant data from Arize AX, summarize it in plain English, and point out anything that needs attention. **Get Prompt** > Pull the relevant data from Arize AX, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Arize AX working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Arize AX API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Arize AX account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Arize AX. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Arize AX actions to the runtime in a format your agent can reliably use. | 24 tools for Arize AX are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Arize AX to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Arize AX in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Arize AX key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Arize AX Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### Connection succeeds but no tools appear Reconnect Arize AX from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Arize AX tools Arize AX tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Arize AX call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Arize AX returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Arize AX has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Arize AX integration? Yes. ClawLink is the fastest way to connect Hermes to Arize AX: link your Arize AX account once in the browser and Hermes Agent can call the Arize AX API through 24 ready-made tools — no custom code or token handling. ### How do I connect Arize AX to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Arize AX in the dashboard and Hermes can use it from the next message — no config files, and the Arize AX key you paste is stored server-side instead of in your environment. ### How long does it take to connect Arize AX to Hermes Agent? About two minutes. Sign in, click Connect next to Arize AX in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Arize AX up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Arize AX working from chat. ### Hermes paired but still can't use Arize AX Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [DataRobot tools](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Connect Chatbotkit](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API tools](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.