# How to connect Lyzr to Hermes Agent (paste one key, 22 tools) > Connect Lyzr to Hermes with ClawLink: paste your Lyzr key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/lyzr Most guides for giving Hermes Agent Lyzr 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 Lyzr setup: pair once in the browser and your always-on Hermes agent can act on Lyzr 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 Lyzr. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Lyzr** — 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 lyzr # connect Lyzr (browser OAuth) npx -y @useclawlink/cli actions lyzr # list available actions npx -y @useclawlink/cli run lyzr --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 Lyzr in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Lyzr API key once. Verify the connection by asking Hermes: > Pull the relevant data from Lyzr, 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 Lyzr is connected in the dashboard, that agent calls the same 22 Lyzr 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). ## Lyzr MCP for Hermes Looking for a Lyzr MCP server for Hermes Agent? ClawLink connects Lyzr to Hermes Agent and exposes 22 Lyzr 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 Lyzr integration](https://claw-link.dev/openclaw/lyzr) works the same way. ## What the Hermes Agent Lyzr integration can do 22 Lyzr tools are ready for Hermes Agent once the account is connected. The 20 below are the ones people reach for most; your agent can call all 22. ### 20 of 22 Lyzr tools for Hermes | Tool | What it does | |---|---| | **Get agent** `lyzr_get_agent` | Return the current configuration and status of one Agent Studio agent by ID | | **Get knowledge base** `lyzr_get_knowledge_base` | Return one Lyzr Knowledge Base configuration by its known RAG configuration ID | | **Get simulation overview** `lyzr_get_simulation_overview` | Return aggregate Agent Simulation counts and average evaluation pass rate for the connected | | **List agent schedules** `lyzr_list_agent_schedules` | Return one page of agent cron schedules, optionally filtered by user, agent, or active state | | **List agent simulation issues** `lyzr_list_agent_simulation_issues` | Return recent performance, error, and Responsible AI issues across monitored agents, optionally | | **List agents** `lyzr_list_agents` | Return all Agent Studio agents owned by the connected API key, including IDs needed by | | **List rai policies** `lyzr_list_rai_policies` | Return Responsible AI policies owned by the authenticated user, including policy IDs and | | **List superflow executions** `lyzr_list_superflow_executions` | Return one page of SuperFlow execution records, optionally filtered by workflow and execution | | **List superflow workflows** `lyzr_list_superflow_workflows` | Return all SuperFlow workflow definitions accessible to the connected API key, including | | **List voice agents** `lyzr_list_voice_agents` | Return saved Voice agents accessible to the connected organization, including IDs used to | | **List voice transcripts** `lyzr_list_voice_transcripts` | Return one page of accessible Voice call transcripts, optionally filtered by agent, session | | **Retrieve knowledge** `lyzr_retrieve_knowledge` | Retrieve relevant documents from a known Lyzr Knowledge Base using configurable basic, MMR | | **Search memories** `lyzr_search_memories` | Semantically search stored memories for one owner, within one session or across that owner's | | **Add memory messages** `lyzr_add_memory_messages` | Store a batch of conversation messages in Lyzr Memory for an owner, session, and optional | | **Chat with agent** `lyzr_chat_with_agent` | Send a message or message history to an active Agent Studio agent and return its synchronous | | **Create agent** `lyzr_create_agent` | Create a single-task Agent Studio agent with an LLM provider, model, instructions, and optional | | **Create agent schedule** `lyzr_create_agent_schedule` | Create a cron schedule that runs one Agent Studio agent with a message in a specified timezone | | **Evaluate text with rai policy** `lyzr_evaluate_text_with_rai_policy` | Apply one owned Responsible AI policy to text and return processed text, block decisions | | **Set agent status** `lyzr_set_agent_status` | Activate or deactivate an Agent Studio agent | | **Clear memory session** `lyzr_clear_memory_session` | Permanently clear messages and memories for one explicit owner and session in Lyzr Memory | ## Example prompts **Get Agent** > Pull the relevant data from Lyzr, summarize it in plain English, and point out anything that needs attention. **Get Knowledge Base** > Pull the relevant data from Lyzr, summarize it in plain English, and point out anything that needs attention. **Get Simulation Overview** > Pull the relevant data from Lyzr, summarize it in plain English, and point out anything that needs attention. **List Agent Schedules** > List the relevant items in Lyzr, group them by priority, and recommend what Hermes should do next. ## 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 Lyzr working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Lyzr API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Lyzr 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 Lyzr. | 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 Lyzr actions to the runtime in a format your agent can reliably use. | 22 tools for Lyzr are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Lyzr 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 Lyzr in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the Lyzr 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 Lyzr 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 Lyzr 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 Lyzr tools Lyzr 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 Lyzr 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. ### Lyzr 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 Lyzr 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 Lyzr integration? Yes. ClawLink is the fastest way to connect Hermes to Lyzr: link your Lyzr account once in the browser and Hermes Agent can call the Lyzr API through 22 ready-made tools — no custom code or token handling. ### How do I connect Lyzr 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 Lyzr in the dashboard and Hermes can use it from the next message — no config files, and the Lyzr key you paste is stored server-side instead of in your environment. ### How long does it take to connect Lyzr to Hermes Agent? About two minutes. Sign in, click Connect next to Lyzr in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Lyzr 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 Lyzr working from chat. ### Hermes paired but still can't use Lyzr 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 - [Hermes DataRobot integration](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.