# How to connect Whoisfreaks to Hermes Agent (paste one key, 17 tools) > Connect Whoisfreaks to Hermes with ClawLink: paste your Whoisfreaks key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/whoisfreaks Most guides for giving Hermes Agent Whoisfreaks 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 Whoisfreaks setup: pair once in the browser and your always-on Hermes agent can act on Whoisfreaks 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 Whoisfreaks. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Whoisfreaks** — 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 whoisfreaks # connect Whoisfreaks (browser OAuth) npx -y @useclawlink/cli actions whoisfreaks # list available actions npx -y @useclawlink/cli run whoisfreaks --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 Whoisfreaks in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Whoisfreaks API key once. Verify the connection by asking Hermes: > Use Whoisfreaks to asn whois lookup 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 Whoisfreaks is connected in the dashboard, that agent calls the same 17 Whoisfreaks 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). ## Whoisfreaks MCP for Hermes Looking for a Whoisfreaks MCP server for Hermes Agent? ClawLink connects Whoisfreaks to Hermes Agent and exposes 17 Whoisfreaks 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 Whoisfreaks integration](https://claw-link.dev/openclaw/whoisfreaks) works the same way. ## What the Hermes Agent Whoisfreaks integration can do 17 Whoisfreaks tools are ready for Hermes Agent once the account is connected. ### All 17 Whoisfreaks tools for Hermes | Tool | What it does | |---|---| | **Asn whois lookup** `whoisfreaks_asn_whois_lookup` | Retrieve comprehensive ASN WHOIS information including ownership, network infrastructure, and | | **Bulk dns lookup** `whoisfreaks_bulk_dns_lookup` | Process multiple domains or IPs simultaneously, returning all DNS records in a single request | | **Bulk domain availability check** `whoisfreaks_bulk_domain_availability_check` | Check availability of multiple domains in one request (max 100 domains) | | **Bulk whois lookup** `whoisfreaks_bulk_whois_lookup` | Query WHOIS information for up to 100 domains in a single request | | **Dns live lookup** `whoisfreaks_dns_live_lookup` | Perform real-time DNS record resolution for network diagnostics and configuration verification | | **Domain availability check** `whoisfreaks_domain_availability_check` | Check if a domain is available for registration with optional suggestions | | **Get domainer files status** `whoisfreaks_get_domainer_files_status` | Check availability and update status of domain data files including newly registered, expired | | **Ip geolocation lookup** `whoisfreaks_ip_geolocation_lookup` | Retrieve geographic location information for an IP address including country, city | | **Ip whois lookup** `whoisfreaks_ip_whois_lookup` | Retrieve comprehensive WHOIS information for an IP address including organization, ISP, and | | **Security threat lookup** `whoisfreaks_security_threat_lookup` | Check if an IP address is associated with malicious activity, security threats, or appears on | | **Ssl certificate lookup** `whoisfreaks_ssl_certificate_lookup` | Fetch live SSL certificate with full secure cert chain, validity dates, and issuer information | | **Subdomains lookup** `whoisfreaks_subdomains_lookup` | Discover all subdomains associated with a domain name | | **Whois historical lookup** `whoisfreaks_whois_historical_lookup` | Access historical domain records from comprehensive database with up to 100 records per page | | **Whois live lookup v2** `whoisfreaks_whois_live_lookup_v2` | Fetch real-time WHOIS domain data using v2.0 endpoint | | **Whois reverse lookup by company** `whoisfreaks_whois_reverse_lookup_by_company` | Search for domains registered by a specific company or organization using reverse WHOIS lookup | | **Whois reverse lookup by email** `whoisfreaks_whois_reverse_lookup_by_email` | Search for domains registered with a specific email address | | **Whois reverse lookup by owner** `whoisfreaks_whois_reverse_lookup_by_owner` | Search for domains registered by a specific owner name using reverse WHOIS lookup | ## Example prompts **Asn Whois Lookup** > Use Whoisfreaks to asn whois lookup and walk me through the result in plain English. **Bulk Dns Lookup** > Use Whoisfreaks to bulk dns lookup and walk me through the result in plain English. **Bulk Domain Availability Check** > Use Whoisfreaks to bulk domain availability check and walk me through the result in plain English. **Bulk Whois Lookup** > Use Whoisfreaks to bulk whois lookup 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 Whoisfreaks working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Whoisfreaks API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Whoisfreaks 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 Whoisfreaks. | 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 Whoisfreaks actions to the runtime in a format your agent can reliably use. | 17 tools for Whoisfreaks are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Whoisfreaks 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 Whoisfreaks in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Whoisfreaks 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 Whoisfreaks 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 Whoisfreaks 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 Whoisfreaks tools Whoisfreaks 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 Whoisfreaks 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. ### Whoisfreaks 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 Whoisfreaks 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 Whoisfreaks integration? Yes. ClawLink is the fastest way to connect Hermes to Whoisfreaks: link your Whoisfreaks account once in the browser and Hermes Agent can call the Whoisfreaks API through 17 ready-made tools — no custom code or token handling. ### How do I connect Whoisfreaks 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 Whoisfreaks in the dashboard and Hermes can use it from the next message — no config files, and the Whoisfreaks key you paste is stored server-side instead of in your environment. ### How long does it take to connect Whoisfreaks to Hermes Agent? About two minutes. Sign in, click Connect next to Whoisfreaks in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Whoisfreaks 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 Whoisfreaks working from chat. ### Hermes paired but still can't use Whoisfreaks 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 - [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [Connect 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.