# How to connect IPRegistry to OpenClaw (paste one key, 5 tools) > Connect IPRegistry to OpenClaw with ClawLink: paste your IPRegistry key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ip-registry The usual route to IPRegistry access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical IPRegistry setup: install one ClawHub skill, connect IPRegistry in the browser, and OpenClaw can call real IPRegistry actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to IPRegistry. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect IPRegistry** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 ip-registry # connect IPRegistry (browser OAuth) npx -y @useclawlink/cli actions ip-registry # list available actions npx -y @useclawlink/cli run ip-registry --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect IPRegistry in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your IPRegistry API key once. Verify the connection by asking OpenClaw: > Use IPRegistry to batch lookup asns and walk me through the result in plain English. ### Using a different agent? The OpenClaw 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 IPRegistry is connected in the dashboard, that agent calls the same 5 IPRegistry 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). ## IPRegistry MCP for OpenClaw Looking for a IPRegistry MCP server for OpenClaw? ClawLink connects IPRegistry to OpenClaw and exposes 5 IPRegistry 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 Hermes instead? The [Hermes IPRegistry integration](https://claw-link.dev/hermes/ip-registry) works the same way. ## What the OpenClaw IPRegistry integration can do 5 IPRegistry tools are ready for OpenClaw once the account is connected. ### All 5 IPRegistry tools for OpenClaw | Tool | What it does | |---|---| | **Batch lookup asns** `ip_registry_batch_lookup_asns` | Return ordered Autonomous System lookup results for 1 to 16 ASNs; an invalid item is returned | | **Batch lookup ips** `ip_registry_batch_lookup_ips` | Return ordered lookup results for 1 to 1024 public IP addresses; an invalid item is returned as | | **Lookup asn** `ip_registry_lookup_asn` | Return organization, country, registry, network-prefix, and relationship data for one public | | **Lookup ip** `ip_registry_lookup_ip` | Return geolocation, network, company, carrier, time-zone, currency, and threat data for one | | **Parse user agents** `ip_registry_parse_user_agents` | Parse 1 to 256 raw User-Agent strings into browser or application, device, rendering-engine | ## Example prompts **Batch Lookup Asns** > Use IPRegistry to batch lookup asns and walk me through the result in plain English. **Batch Lookup Ips** > Use IPRegistry to batch lookup ips and walk me through the result in plain English. **Lookup Asn** > Use IPRegistry to lookup asn and walk me through the result in plain English. **Lookup Ip** > Use IPRegistry to lookup ip 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want IPRegistry working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the IPRegistry API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected IPRegistry 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 IPRegistry. | 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 IPRegistry actions to the runtime in a format your agent can reliably use. | 5 tools for IPRegistry are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes IPRegistry 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 OpenClaw users instead. You install the plugin once, connect IPRegistry in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the IPRegistry 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. ### OpenClaw installed the IPRegistry skill but can't call the tools The ClawHub skill teaches OpenClaw about IPRegistry, but the calls run through the ClawLink plugin and your connected account. Make sure IPRegistry is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect IPRegistry 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 IPRegistry tools IPRegistry 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 IPRegistry 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. ### IPRegistry 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 IPRegistry has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw IPRegistry integration? Yes. ClawLink is the fastest way to connect OpenClaw to IPRegistry: link your IPRegistry account once in the browser and OpenClaw can call the IPRegistry API through 5 ready-made tools — no custom code or token handling. ### How do I add IPRegistry to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink IPRegistry skill from ClawHub, then you click Connect in the dashboard to authorize IPRegistry. OpenClaw calls the tools from the next message — no config files, and the IPRegistry key you paste is stored server-side instead of in your environment. ### How long does it take to connect IPRegistry to OpenClaw? About two minutes. Sign in, click Connect next to IPRegistry in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring IPRegistry up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want IPRegistry working from chat. ### OpenClaw installed the IPRegistry skill but can't call the tools The ClawHub skill teaches OpenClaw about IPRegistry, but the calls run through the ClawLink plugin and your connected account. Make sure IPRegistry is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.