# How to connect Keyzy to Hermes Agent (paste one key, 14 tools) > Connect Keyzy to Hermes with ClawLink: paste your Keyzy key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/keyzy Most guides for giving Hermes Agent Keyzy 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 Keyzy setup: pair once in the browser and your always-on Hermes agent can act on Keyzy 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 Keyzy. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Keyzy** — 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 keyzy # connect Keyzy (browser OAuth) npx -y @useclawlink/cli actions keyzy # list available actions npx -y @useclawlink/cli run keyzy --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 Keyzy in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Keyzy API key once. Verify the connection by asking Hermes: > Pull the relevant data from Keyzy, 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 Keyzy is connected in the dashboard, that agent calls the same 14 Keyzy 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). ## Keyzy MCP for Hermes Looking for a Keyzy MCP server for Hermes Agent? ClawLink connects Keyzy to Hermes Agent and exposes 14 Keyzy 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 Keyzy integration](https://claw-link.dev/openclaw/keyzy) works the same way. ## What the Hermes Agent Keyzy integration can do 14 Keyzy tools are ready for Hermes Agent once the account is connected. The 12 below are the ones people reach for most; your agent can call all 14. ### 12 of 14 Keyzy tools for Hermes | Tool | What it does | |---|---| | **Get license** `keyzy_get_license` | Return customer, SKU, type, registration, and validity-period details for one license serial | | **List activations** `keyzy_list_activations` | Return all activation records associated with one license serial number | | **List license products** `keyzy_list_license_products` | Return the products associated with a license serial, including product codes needed for | | **Preview dealer license registration** `keyzy_preview_dealer_license_registration` | Check an unregistered dealer license and return the customer-registration details before | | **Download encrypted license file** `keyzy_download_encrypted_license_file` | Activate or renew a semi-online Keyzy license and download its encrypted offline license file | | **Register license** `keyzy_register_license` | Assign an available license for an SKU to a customer and return the new serial number | | **Update activation** `keyzy_update_activation` | Activate or deactivate an existing activation record by numeric ID | | **Update license sku** `keyzy_update_license_sku` | Move a license to a new SKU, changing its license type to the destination SKU's type | | **Update license term** `keyzy_update_license_term` | Update the validity start and/or required end time of a subscription or trial license | | **Validate license** `keyzy_validate_license` | Validate a Keyzy license for a product | | **Register dealer license** `keyzy_register_dealer_license` | Preview an offline dealer license, verify its SKU, then irreversibly register it to a customer | | **Upgrade license** `keyzy_upgrade_license` | Irreversibly exchange a current license for an upgrade license | ## Example prompts **Get License** > Pull the relevant data from Keyzy, summarize it in plain English, and point out anything that needs attention. **List Activations** > List the relevant items in Keyzy, group them by priority, and recommend what Hermes should do next. **List License Products** > List the relevant items in Keyzy, group them by priority, and recommend what Hermes should do next. **Preview Dealer License Registration** > Use Keyzy to preview dealer license registration and walk me through the result in plain English. ## 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 Keyzy working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Keyzy API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Keyzy 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 Keyzy. | 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 Keyzy actions to the runtime in a format your agent can reliably use. | 14 tools for Keyzy are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Keyzy 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 Keyzy in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Keyzy 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 Keyzy 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 Keyzy 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 Keyzy tools Keyzy 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 Keyzy 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. ### Keyzy 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 Keyzy 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 Keyzy integration? Yes. ClawLink is the fastest way to connect Hermes to Keyzy: link your Keyzy account once in the browser and Hermes Agent can call the Keyzy API through 14 ready-made tools — no custom code or token handling. ### How do I connect Keyzy 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 Keyzy in the dashboard and Hermes can use it from the next message — no config files, and the Keyzy key you paste is stored server-side instead of in your environment. ### How long does it take to connect Keyzy to Hermes Agent? About two minutes. Sign in, click Connect next to Keyzy in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Keyzy 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 Keyzy working from chat. ### Hermes paired but still can't use Keyzy 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 GitHub integration](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.