# How to connect Devolens / Cryptolens to Hermes Agent (paste one key, 10 tools) > Connect Devolens / Cryptolens to Hermes with ClawLink: paste your Devolens / Cryptolens key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/devolens Most guides for giving Hermes Agent Devolens / Cryptolens 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 Devolens / Cryptolens setup: pair once in the browser and your always-on Hermes agent can act on Devolens / Cryptolens 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 Devolens / Cryptolens. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Devolens / Cryptolens** — 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 devolens # connect Devolens / Cryptolens (browser OAuth) npx -y @useclawlink/cli actions devolens # list available actions npx -y @useclawlink/cli run devolens --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 Devolens / Cryptolens in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Devolens / Cryptolens API key once. Verify the connection by asking Hermes: > Pull the relevant data from Devolens / Cryptolens, 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 Devolens / Cryptolens is connected in the dashboard, that agent calls the same 10 Devolens / Cryptolens 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). ## Devolens / Cryptolens MCP for Hermes Looking for a Devolens / Cryptolens MCP server for Hermes Agent? ClawLink connects Devolens / Cryptolens to Hermes Agent and exposes 10 Devolens / Cryptolens 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 Devolens / Cryptolens integration](https://claw-link.dev/openclaw/devolens) works the same way. ## What the Hermes Agent Devolens / Cryptolens integration can do 10 Devolens / Cryptolens tools are ready for Hermes Agent once the account is connected. ### All 10 Devolens / Cryptolens tools for Hermes | Tool | What it does | |---|---| | **Get license key** `devolens_get_license_key` | Retrieve one license key and optional activation metadata by its product ID and key string | | **List customers** `devolens_list_customers` | Search or list customers visible to the connected Cryptolens account, including | | **List daily usage aggregates** `devolens_list_daily_usage_aggregates` | Return one page of daily Cryptolens usage aggregates, optionally filtered by product and | | **List license keys** `devolens_list_license_keys` | List and search one page of license keys for a Cryptolens product | | **List license templates** `devolens_list_license_templates` | Return the license templates available to the connected Cryptolens account | | **List license users** `devolens_list_license_users` | Return registered Cryptolens license users, optionally limited to one customer | | **List messages** `devolens_list_messages` | Return Cryptolens account messages, optionally filtered by channel or creation time | | **List products** `devolens_list_products` | Return the Cryptolens products visible to the connected access token | | **List resellers** `devolens_list_resellers` | Search or list resellers visible to the connected Cryptolens account | | **List web API logs** `devolens_list_web_api_logs` | Inspect one page of Cryptolens Web API request logs with optional product, license-key | ## Example prompts **Get License Key** > Pull the relevant data from Devolens / Cryptolens, summarize it in plain English, and point out anything that needs attention. **List Customers** > List the relevant items in Devolens / Cryptolens, group them by priority, and recommend what Hermes should do next. **List Daily Usage Aggregates** > List the relevant items in Devolens / Cryptolens, group them by priority, and recommend what Hermes should do next. **List License Keys** > List the relevant items in Devolens / Cryptolens, 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 Devolens / Cryptolens working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Devolens / Cryptolens API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Devolens / Cryptolens 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 Devolens / Cryptolens. | 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 Devolens / Cryptolens actions to the runtime in a format your agent can reliably use. | 10 tools for Devolens / Cryptolens are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Devolens / Cryptolens 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 Devolens / Cryptolens in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Devolens / Cryptolens 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 Devolens / Cryptolens 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 Devolens / Cryptolens 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 Devolens / Cryptolens tools Devolens / Cryptolens 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 Devolens / Cryptolens 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. ### Devolens / Cryptolens 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 Devolens / Cryptolens 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 Devolens / Cryptolens integration? Yes. ClawLink is the fastest way to connect Hermes to Devolens / Cryptolens: link your Devolens / Cryptolens account once in the browser and Hermes Agent can call the Devolens / Cryptolens API through 10 ready-made tools — no custom code or token handling. ### How do I connect Devolens / Cryptolens 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 Devolens / Cryptolens in the dashboard and Hermes can use it from the next message — no config files, and the Devolens / Cryptolens key you paste is stored server-side instead of in your environment. ### How long does it take to connect Devolens / Cryptolens to Hermes Agent? About two minutes. Sign in, click Connect next to Devolens / Cryptolens in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Devolens / Cryptolens 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 Devolens / Cryptolens working from chat. ### Hermes paired but still can't use Devolens / Cryptolens 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 - [Connect GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Hermes PagerDuty integration](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.