# How to connect Zernio to Hermes Agent (no API keys) > Connect Zernio to Hermes with ClawLink in one click — 51 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/zernio Most guides for giving Hermes Agent Zernio 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 Zernio setup: pair once in the browser and your always-on Hermes agent can act on Zernio 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 Zernio. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Zernio** — 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 zernio # connect Zernio (browser OAuth) npx -y @useclawlink/cli actions zernio # list available actions npx -y @useclawlink/cli run zernio --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 Zernio in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Zernio to mcp account groups list account groups 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 Zernio is connected in the dashboard, that agent calls the same 51 Zernio 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). ## Zernio MCP for Hermes Looking for a Zernio MCP server for Hermes Agent? ClawLink connects Zernio to Hermes Agent and exposes 51 Zernio 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 Zernio integration](https://claw-link.dev/openclaw/zernio) works the same way. ## What the Hermes Agent Zernio integration can do 51 Zernio tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 51. ### 30 of 51 Zernio tools for Hermes | Tool | What it does | |---|---| | **Mcp account groups list account groups** `zernio_mcp_account_groups_list_account_groups` | List groups | | **Mcp accounts get** `zernio_mcp_accounts_get` | Get account details for a specific platform | | **Mcp accounts get account health** `zernio_mcp_accounts_get_account_health` | Check account health | | **Mcp accounts get all accounts health** `zernio_mcp_accounts_get_all_accounts_health` | Check accounts health | | **Mcp accounts get follower stats** `zernio_mcp_accounts_get_follower_stats` | Get follower stats | | **Mcp accounts list** `zernio_mcp_accounts_list` | List all connected social media accounts | | **Mcp analytics get analytics** `zernio_mcp_analytics_get_analytics` | Get post analytics | | **Mcp analytics get best time to post** `zernio_mcp_analytics_get_best_time_to_post` | Get best times to post | | **Mcp analytics get daily metrics** `zernio_mcp_analytics_get_daily_metrics` | Get daily aggregated metrics Args: platform: Filter by platform (e.g | | **Mcp analytics get post timeline** `zernio_mcp_analytics_get_post_timeline` | Get post analytics timeline Args: post_id: The post to fetch timeline for | | **Mcp comments get inbox post comments** `zernio_mcp_comments_get_inbox_post_comments` | Get post comments | | **Mcp comments list inbox comments** `zernio_mcp_comments_list_inbox_comments` | List commented posts | | **Mcp docs search** `zernio_mcp_docs_search` | Search across the Late API documentation to find relevant information, code examples, API | | **Mcp media check upload status** `zernio_mcp_media_check_upload_status` | Check the status of an upload token and get uploaded file URLs | | **Mcp mentions list inbox mentions** `zernio_mcp_mentions_list_inbox_mentions` | List mentions | | **Mcp posts get** `zernio_mcp_posts_get` | Get full details of a specific post including content, status, and scheduling info | | **Mcp posts list** `zernio_mcp_posts_list` | List posts with optional filtering by status | | **Mcp posts list failed** `zernio_mcp_posts_list_failed` | List all failed posts that can be retried | | **Mcp profiles get** `zernio_mcp_profiles_get` | Get details of a specific profile including name, description, and color | | **Mcp profiles list** `zernio_mcp_profiles_list` | List all profiles | | **Mcp queue get next queue slot** `zernio_mcp_queue_get_next_queue_slot` | Get next available slot | | **Mcp queue list queue slots** `zernio_mcp_queue_list_queue_slots` | List schedules | | **Mcp search tools** `zernio_mcp_search_tools` | Search for tools using natural language | | **Mcp tracking tags get tracking tag stats** `zernio_mcp_tracking_tags_get_tracking_tag_stats` | Get aggregated event stats | | **Mcp tracking tags list tracking tags** `zernio_mcp_tracking_tags_list_tracking_tags` | List tracking tags | | **Mcp usage get usage** `zernio_mcp_usage_get_usage` | Usage snapshot (default) or billed-spend metering (with params) Args: reconcile: Snapshot mode | | **Mcp accounts move account to profile** `zernio_mcp_accounts_move_account_to_profile` | Move account to another profile | | **Mcp call tool** `zernio_mcp_call_tool` | Call a tool by name with the given arguments | | **Mcp comments reply to inbox post** `zernio_mcp_comments_reply_to_inbox_post` | Reply to comment | | **Mcp media generate upload link** `zernio_mcp_media_generate_upload_link` | Generate a unique upload URL for the user to upload files via browser | ## Example prompts **Mcp Account Groups List Account Groups** > Use Zernio to mcp account groups list account groups and walk me through the result in plain English. **Mcp Accounts Get** > Use Zernio to mcp accounts get and walk me through the result in plain English. **Mcp Accounts Get Account Health** > Use Zernio to mcp accounts get account health and walk me through the result in plain English. **Mcp Accounts Get All Accounts Health** > Use Zernio to mcp accounts get all accounts health and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app 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 Zernio working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Zernio app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Zernio through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Zernio. | 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 Zernio actions to the runtime in a format your agent can reliably use. | 51 tools for Zernio are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Zernio 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 Zernio in the browser, and the 51 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Zernio 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 Zernio 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 Zernio tools Zernio 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 Zernio 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. ### Zernio 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. ### OAuth finished in the browser but the account is still missing Try reconnecting Zernio and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Hermes Agent Zernio integration? Yes. ClawLink is the fastest way to connect Hermes to Zernio: link your Zernio account once in the browser and Hermes Agent can call the Zernio API through 51 ready-made tools — no custom code or token handling. ### How do I connect Zernio 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 Zernio in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Zernio to Hermes Agent? About two minutes. Sign in, click Connect next to Zernio in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Zernio up myself? The alternative to ClawLink is usually manual OAuth app 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 Zernio working from chat. ### Hermes paired but still can't use Zernio 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 Stack Exchange integration](https://claw-link.dev/hermes/stack-exchange) — Search and browse questions, answers, and developer knowledge - [Hermes TikTok public data integration](https://claw-link.dev/hermes/tiktok-data) — Read any public TikTok profile, video, comments, hashtag or search. Read-only and not your account: nothing to connect, paid per call from credit - [Connect X (Twitter)](https://claw-link.dev/hermes/twitter) — Post tweets, manage lists, search content, and analyze engagement