# How to connect Ritekit to Hermes Agent (paste one key, 14 tools) > Connect Ritekit to Hermes with ClawLink: paste your Ritekit 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/ritekit Most guides for giving Hermes Agent Ritekit 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 Ritekit setup: pair once in the browser and your always-on Hermes agent can act on Ritekit 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 Ritekit. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Ritekit** — 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 ritekit # connect Ritekit (browser OAuth) npx -y @useclawlink/cli actions ritekit # list available actions npx -y @useclawlink/cli run ritekit --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 Ritekit in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ritekit API key once. Verify the connection by asking Hermes: > Use Ritekit to auto hashtag and walk me through the result in plain English. ### 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 Ritekit is connected in the dashboard, that agent calls the same 14 Ritekit 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). ## Ritekit MCP for Hermes Looking for a Ritekit MCP server for Hermes Agent? ClawLink connects Ritekit to Hermes Agent and exposes 14 Ritekit 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 Ritekit integration](https://claw-link.dev/openclaw/ritekit) works the same way. ## What the Hermes Agent Ritekit integration can do 14 Ritekit tools are ready for Hermes Agent once the account is connected. The 13 below are the ones people reach for most; your agent can call all 14. ### 13 of 14 Ritekit tools for Hermes | Tool | What it does | |---|---| | **Auto hashtag** `ritekit_auto_hashtag` | Automatically add relevant hashtags to a given post | | **Banned instagram hashtags** `ritekit_banned_instagram_hashtags` | Identify which hashtags are banned on Instagram | | **Detect disposable email** `ritekit_detect_disposable_email` | Detect if an email address is disposable | | **Detect email typo** `ritekit_detect_email_typo` | Detect common typos in email addresses and suggest corrections | | **Freemail detection** `ritekit_freemail_detection` | Detect whether an email address belongs to a free email provider | | **Get client ID** `ritekit_get_client_id` | Retrieve stored RiteKit client_id | | **Get client secret** `ritekit_get_client_secret` | Retrieve stored RiteKit client_secret | | **Get full email insights** `ritekit_get_full_email_insights` | Retrieve comprehensive email address insights including full name, free mail detection | | **Hashtag suggestions** `ritekit_hashtag_suggestions` | Get hashtag suggestions for a given text | | **List link ads** `ritekit_list_link_ads` | Retrieve a list of link ads | | **Text to image** `ritekit_text_to_image` | Convert a quote into a styled image | | **Get access token** `ritekit_get_access_token` | Obtain a RiteKit access token | | **Shorten link** `ritekit_shorten_link` | Shorten a URL with a specified CTA | ## Example prompts **Auto Hashtag** > Use Ritekit to auto hashtag and walk me through the result in plain English. **Banned Instagram Hashtags** > Use Ritekit to banned instagram hashtags and walk me through the result in plain English. **Detect Disposable Email** > Use Ritekit to detect disposable email and walk me through the result in plain English. **Detect Email Typo** > Use Ritekit to detect email typo 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 Ritekit working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Ritekit API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ritekit 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 Ritekit. | 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 Ritekit actions to the runtime in a format your agent can reliably use. | 14 tools for Ritekit are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Ritekit 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 Ritekit in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Ritekit 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 Ritekit 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 Ritekit 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 Ritekit tools Ritekit 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 Ritekit 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. ### Ritekit 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 Ritekit 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 Ritekit integration? Yes. ClawLink is the fastest way to connect Hermes to Ritekit: link your Ritekit account once in the browser and Hermes Agent can call the Ritekit API through 14 ready-made tools — no custom code or token handling. ### How do I connect Ritekit 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 Ritekit in the dashboard and Hermes can use it from the next message — no config files, and the Ritekit key you paste is stored server-side instead of in your environment. ### How long does it take to connect Ritekit to Hermes Agent? About two minutes. Sign in, click Connect next to Ritekit in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Ritekit 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 Ritekit working from chat. ### Hermes paired but still can't use Ritekit 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 ActiveCampaign](https://claw-link.dev/hermes/activecampaign) — Marketing automation, CRM, and email marketing - [Hermes Benchmark Email integration](https://claw-link.dev/hermes/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences