# How to connect Ipdata.co to Hermes Agent (paste one key, 28 tools) > Connect Ipdata.co to Hermes with ClawLink: paste your Ipdata.co key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/ipdata-co Most guides for giving Hermes Agent Ipdata.co 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 Ipdata.co setup: pair once in the browser and your always-on Hermes agent can act on Ipdata.co 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 Ipdata.co. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Ipdata.co** — 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 ipdata-co # connect Ipdata.co (browser OAuth) npx -y @useclawlink/cli actions ipdata-co # list available actions npx -y @useclawlink/cli run ipdata-co --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 Ipdata.co in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ipdata.co API key once. Verify the connection by asking Hermes: > Use Ipdata.co to advanced asn 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 Ipdata.co is connected in the dashboard, that agent calls the same 28 Ipdata.co 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). ## Ipdata.co MCP for Hermes Looking for a Ipdata.co MCP server for Hermes Agent? ClawLink connects Ipdata.co to Hermes Agent and exposes 28 Ipdata.co 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 Ipdata.co integration](https://claw-link.dev/openclaw/ipdata-co) works the same way. ## What the Hermes Agent Ipdata.co integration can do 28 Ipdata.co tools are ready for Hermes Agent once the account is connected. ### All 28 Ipdata.co tools for Hermes | Tool | What it does | |---|---| | **Advanced asn lookup** `ipdata_co_advanced_asn_lookup` | Perform advanced ASN lookup returning prefixes, peers, and registry details | | **Eu lookup specific ip** `ipdata_co_eu_lookup_specific_ip` | Lookup geolocation, threat intel, and network data for a specific IP address using the EU data | | **Field calling code** `ipdata_co_field_calling_code` | Fetch the international calling_code for an IP's country | | **Field carrier** `ipdata_co_field_carrier` | Retrieve mobile carrier information (name, MCC, MNC) for an IP address | | **Field city** `ipdata_co_field_city` | Return only city for an IP | | **Field continent code** `ipdata_co_field_continent_code` | Retrieve the continent code for a given IP address | | **Field continent name** `ipdata_co_field_continent_name` | Return only continent name for an IP | | **Field count** `ipdata_co_field_count` | Return only the request count made by your API key in the last 24 hours | | **Field country code** `ipdata_co_field_country_code` | Return only country_code for an IP | | **Field country name** `ipdata_co_field_country_name` | Get the country name for an IP address using ipdata.co geolocation API | | **Field currency** `ipdata_co_field_currency` | Return only currency object for an IP | | **Field emoji flag** `ipdata_co_field_emoji_flag` | Return only emoji flag for an IP | | **Field emoji unicode** `ipdata_co_field_emoji_unicode` | Return only emoji_unicode for an IP | | **Field ip** `ipdata_co_field_ip` | Retrieve the public IP address of the calling client | | **Field is eu** `ipdata_co_field_is_eu` | Return only is_eu for an IP | | **Field languages** `ipdata_co_field_languages` | Return only the languages array for an IP | | **Field latitude** `ipdata_co_field_latitude` | Return only the latitude for an IP | | **Field longitude** `ipdata_co_field_longitude` | Return only longitude for an IP | | **Field postal** `ipdata_co_field_postal` | Return only postal code for an IP | | **Field region** `ipdata_co_field_region` | Return only region for an IP | | **Field region code** `ipdata_co_field_region_code` | Return only region_code for an IP | | **Field threat** `ipdata_co_field_threat` | Retrieve threat intelligence data for a specific IP address or the calling IP | | **Field time zone** `ipdata_co_field_time_zone` | Return only the time_zone object for an IP | | **Ip data basic asn for ip** `ipdata_co_ip_data_basic_asn_for_ip` | Return basic ASN data for a specific IP | | **Ip data company for ip** `ipdata_co_ip_data_company_for_ip` | Retrieve company data for a given IP address | | **Ip data lookup ip v1** `ipdata_co_ip_data_lookup_ip_v1` | Lookup comprehensive IP information (geolocation, network, company, and threat data) in one call | | **Ipdata bulk lookup v1** `ipdata_co_ipdata_bulk_lookup_v1` | Bulk lookup up to 100 IP addresses via ipdata.co | | **Ipdata eu lookup calling ip** `ipdata_co_ipdata_eu_lookup_calling_ip` | Lookup geolocation, network, and threat data for the calling client's IP address using the | ## Example prompts **Advanced Asn Lookup** > Use Ipdata.co to advanced asn lookup and walk me through the result in plain English. **Eu Lookup Specific Ip** > Use Ipdata.co to eu lookup specific ip and walk me through the result in plain English. **Field Calling Code** > Use Ipdata.co to field calling code and walk me through the result in plain English. **Field Carrier** > Use Ipdata.co to field carrier 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 Ipdata.co working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Ipdata.co API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ipdata.co 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 Ipdata.co. | 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 Ipdata.co actions to the runtime in a format your agent can reliably use. | 28 tools for Ipdata.co are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Ipdata.co 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 Ipdata.co in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the Ipdata.co 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 Ipdata.co 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 Ipdata.co 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 Ipdata.co tools Ipdata.co 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 Ipdata.co 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. ### Ipdata.co 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 Ipdata.co 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 Ipdata.co integration? Yes. ClawLink is the fastest way to connect Hermes to Ipdata.co: link your Ipdata.co account once in the browser and Hermes Agent can call the Ipdata.co API through 28 ready-made tools — no custom code or token handling. ### How do I connect Ipdata.co 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 Ipdata.co in the dashboard and Hermes can use it from the next message — no config files, and the Ipdata.co key you paste is stored server-side instead of in your environment. ### How long does it take to connect Ipdata.co to Hermes Agent? About two minutes. Sign in, click Connect next to Ipdata.co in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Ipdata.co 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 Ipdata.co working from chat. ### Hermes paired but still can't use Ipdata.co 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.