# How to connect Kaleido to Hermes Agent (paste one key, 29 tools) > Connect Kaleido to Hermes with ClawLink: paste your Kaleido key once and 29 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/kaleido Most guides for giving Hermes Agent Kaleido 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 Kaleido setup: pair once in the browser and your always-on Hermes agent can act on Kaleido 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 Kaleido. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Kaleido** — 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 kaleido # connect Kaleido (browser OAuth) npx -y @useclawlink/cli actions kaleido # list available actions npx -y @useclawlink/cli run kaleido --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 Kaleido in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Kaleido API key once. Verify the connection by asking Hermes: > Pull the relevant data from Kaleido, 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 Kaleido is connected in the dashboard, that agent calls the same 29 Kaleido 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). ## Kaleido MCP for Hermes Looking for a Kaleido MCP server for Hermes Agent? ClawLink connects Kaleido to Hermes Agent and exposes 29 Kaleido 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 Kaleido integration](https://claw-link.dev/openclaw/kaleido) works the same way. ## What the Hermes Agent Kaleido integration can do 29 Kaleido tools are ready for Hermes Agent once the account is connected. The 27 below are the ones people reach for most; your agent can call all 29. ### 27 of 29 Kaleido tools for Hermes | Tool | What it does | |---|---| | **Get API key** `kaleido_get_api_key` | Retrieve details of a specific API key by its ID | | **Get API keys** `kaleido_get_api_keys` | Retrieve all API keys associated with the organization | | **Get application credentials** `kaleido_get_application_credentials` | Retrieve application credentials for a specific environment | | **Get billing summary** `kaleido_get_billing_summary` | Retrieves a summary of billing data for the specified organization for the current month | | **Get consortia** `kaleido_get_consortia` | Retrieve all consortia associated with the organization | | **Get event streams** `kaleido_get_event_streams` | List all event streams configured on a Kaleido blockchain node's Ethconnect REST API Gateway | | **Get identity proof** `kaleido_get_identity_proof` | Retrieve a specific identity proof for a Kaleido organization | | **Get invitations** `kaleido_get_invitations` | Retrieve all invitations for the current user where they are the target | | **Get memberships** `kaleido_get_memberships` | Retrieve all memberships for the current user | | **Get org billing provider** `kaleido_get_org_billing_provider` | Retrieves billing provider information for a specific organization in Kaleido | | **Get organization** `kaleido_get_organization` | Retrieve details of a specific Kaleido organization by its ID | | **Get organization plan** `kaleido_get_organization_plan` | Retrieve the subscription plan details for a Kaleido organization | | **Get organizations** `kaleido_get_organizations` | Retrieves all organizations that the authenticated user has access to in Kaleido | | **Get plans** `kaleido_get_plans` | Retrieve all available Kaleido subscription plans | | **Get regions** `kaleido_get_regions` | Retrieve all available Kaleido deployment regions and their deployment zones | | **Get releases** `kaleido_get_releases` | Retrieve all available blockchain node software releases from the Kaleido platform | | **Get role by ID** `kaleido_get_role_by_id` | Retrieve a specific user role assignment within a Kaleido organization | | **Get roles** `kaleido_get_roles` | Retrieve all user role assignments for a Kaleido organization | | **Get services** `kaleido_get_services` | Retrieve all services the current user owns or can see | | **Get token factory tokens** `kaleido_get_token_factory_tokens` | Retrieves all token contracts from a Kaleido Token Factory service | | **Get wallet account nonce** `kaleido_get_wallet_account_nonce` | Retrieve the current nonce (transaction count) of a specific HD wallet account | | **Get wallets** `kaleido_get_wallets` | Retrieve HD wallet IDs hosted in the service | | **Add identity proof** `kaleido_add_identity_proof` | Add an x509 identity proof to a Kaleido organization | | **Create API key** `kaleido_create_api_key` | Creates a new API key for the specified Kaleido organization | | **Update org role** `kaleido_update_org_role` | Update the role assignment for a user in a Kaleido organization | | **Update organization** `kaleido_update_organization` | Update a specific organization in Kaleido | | **Upsert organization role** `kaleido_upsert_organization_role` | Upsert (create or update) a role assignment for a user in a Kaleido organization | ## Example prompts **Get Api Key** > Pull the relevant data from Kaleido, summarize it in plain English, and point out anything that needs attention. **Get Api Keys** > Pull the relevant data from Kaleido, summarize it in plain English, and point out anything that needs attention. **Get Application Credentials** > Pull the relevant data from Kaleido, summarize it in plain English, and point out anything that needs attention. **Get Billing Summary** > Pull the relevant data from Kaleido, 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 Kaleido working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Kaleido API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Kaleido 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 Kaleido. | 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 Kaleido actions to the runtime in a format your agent can reliably use. | 29 tools for Kaleido are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Kaleido 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 Kaleido in the browser, and the 29 tools above work from chat. There is no SDK and no config file, and the Kaleido 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 Kaleido 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 Kaleido 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 Kaleido tools Kaleido 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 Kaleido 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. ### Kaleido 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 Kaleido 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 Kaleido integration? Yes. ClawLink is the fastest way to connect Hermes to Kaleido: link your Kaleido account once in the browser and Hermes Agent can call the Kaleido API through 29 ready-made tools — no custom code or token handling. ### How do I connect Kaleido 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 Kaleido in the dashboard and Hermes can use it from the next message — no config files, and the Kaleido key you paste is stored server-side instead of in your environment. ### How long does it take to connect Kaleido to Hermes Agent? About two minutes. Sign in, click Connect next to Kaleido in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Kaleido 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 Kaleido working from chat. ### Hermes paired but still can't use Kaleido 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 tools](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.