# How to connect Ipinfo.io to OpenClaw (paste one key, 27 tools) > Connect Ipinfo.io to OpenClaw with ClawLink: paste your Ipinfo.io key once and 27 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ipinfo-io The usual route to Ipinfo.io 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 Ipinfo.io setup: install one ClawHub skill, connect Ipinfo.io in the browser, and OpenClaw can call real Ipinfo.io 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 Ipinfo.io. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Ipinfo.io** — 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 ipinfo-io # connect Ipinfo.io (browser OAuth) npx -y @useclawlink/cli actions ipinfo-io # list available actions npx -y @useclawlink/cli run ipinfo-io --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 Ipinfo.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ipinfo.io API key once. Verify the connection by asking OpenClaw: > Use Ipinfo.io to batch lite lookup 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 Ipinfo.io is connected in the dashboard, that agent calls the same 27 Ipinfo.io 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). ## Ipinfo.io MCP for OpenClaw Looking for a Ipinfo.io MCP server for OpenClaw? ClawLink connects Ipinfo.io to OpenClaw and exposes 27 Ipinfo.io 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 Ipinfo.io integration](https://claw-link.dev/hermes/ipinfo-io) works the same way. ## What the OpenClaw Ipinfo.io integration can do 27 Ipinfo.io tools are ready for OpenClaw once the account is connected. ### All 27 Ipinfo.io tools for OpenClaw | Tool | What it does | |---|---| | **Batch lite lookup** `ipinfo_io_batch_lite_lookup` | Perform bulk Lite IP lookups for up to 1000 IPs in a single request | | **Batch lookup** `ipinfo_io_batch_lookup` | Perform batch IP lookups to retrieve geolocation and ASN information for multiple IPs in a | | **Get abuse contact** `ipinfo_io_get_abuse_contact` | Retrieve abuse contact and organization information for an IP address | | **Get carrier info** `ipinfo_io_get_carrier_info` | Retrieves mobile carrier information for a given IP address | | **Get city by ip** `ipinfo_io_get_city_by_ip` | Retrieve the city name for a specific IP address | | **Get company info** `ipinfo_io_get_company_info` | Retrieve company/organization information for an IP address | | **Get core field by me** `ipinfo_io_get_core_field_by_me` | Retrieve a specific field from core IP information about the current IP | | **Get country by ip** `ipinfo_io_get_country_by_ip` | Retrieve the two-letter ISO 3166 country code for an IP address | | **Get current ip** `ipinfo_io_get_current_ip` | Retrieve the current public/external IP address | | **Get current ip info** `ipinfo_io_get_current_ip_info` | Retrieve comprehensive IP information about the caller's current IP address | | **Get current loc** `ipinfo_io_get_current_loc` | Retrieve geographic coordinates for the current IP address | | **Get current region** `ipinfo_io_get_current_region` | Retrieve the region/state for the caller's current IP address | | **Get geo by ip** `ipinfo_io_get_geo_by_ip` | Get geolocation data only for an IP address | | **Get hostname by ip** `ipinfo_io_get_hostname_by_ip` | Retrieve the hostname (reverse DNS) for an IP address | | **Get ip by ip** `ipinfo_io_get_ip_by_ip` | Retrieve the IP address for a specified IP as plain text | | **Get ip info** `ipinfo_io_get_ip_info` | Retrieve geolocation and ASN information for an IP address | | **Get ip info by ip** `ipinfo_io_get_ip_info_by_ip` | Retrieve comprehensive information about a specified IP address | | **Get lite field by ip** `ipinfo_io_get_lite_field_by_ip` | Retrieve a specific field from lightweight IP information | | **Get location by ip** `ipinfo_io_get_location_by_ip` | Retrieve geographic coordinates (latitude, longitude) for an IP address | | **Get org by ip** `ipinfo_io_get_org_by_ip` | Retrieve ASN and organization name for an IP address as plain text | | **Get plus field by me** `ipinfo_io_get_plus_field_by_me` | Retrieve a specific field from plus IP information about the current IP | | **Get postal by ip** `ipinfo_io_get_postal_by_ip` | Retrieve the postal/zip code for an IP address | | **Get privacy details** `ipinfo_io_get_privacy_details` | Retrieve privacy/anonymous IP detection flags for an IP address | | **Get region by ip** `ipinfo_io_get_region_by_ip` | Retrieve the region/state for a specified IP address | | **Get timezone by ip** `ipinfo_io_get_timezone_by_ip` | Retrieve the IANA timezone for a given IP address | | **Get token info** `ipinfo_io_get_token_info` | Retrieve API service request limit information by access token | | **Map ips** `ipinfo_io_map_ips` | Create an IPinfo map visualization from a list of IP addresses | ## Example prompts **Batch Lite Lookup** > Use Ipinfo.io to batch lite lookup and walk me through the result in plain English. **Batch Lookup** > Use Ipinfo.io to batch lookup and walk me through the result in plain English. **Get Abuse Contact** > Pull the relevant data from Ipinfo.io, summarize it in plain English, and point out anything that needs attention. **Get Carrier Info** > Pull the relevant data from Ipinfo.io, summarize it in plain English, and point out anything that needs attention. ## 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 Ipinfo.io working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Ipinfo.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ipinfo.io 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 Ipinfo.io. | 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 Ipinfo.io actions to the runtime in a format your agent can reliably use. | 27 tools for Ipinfo.io are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Ipinfo.io 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 Ipinfo.io in the browser, and the 27 tools above work from chat. There is no SDK and no config file, and the Ipinfo.io 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 Ipinfo.io skill but can't call the tools The ClawHub skill teaches OpenClaw about Ipinfo.io, but the calls run through the ClawLink plugin and your connected account. Make sure Ipinfo.io 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 Ipinfo.io 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 Ipinfo.io tools Ipinfo.io 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 Ipinfo.io 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. ### Ipinfo.io 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 Ipinfo.io has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Ipinfo.io integration? Yes. ClawLink is the fastest way to connect OpenClaw to Ipinfo.io: link your Ipinfo.io account once in the browser and OpenClaw can call the Ipinfo.io API through 27 ready-made tools — no custom code or token handling. ### How do I add Ipinfo.io to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ipinfo.io skill from ClawHub, then you click Connect in the dashboard to authorize Ipinfo.io. OpenClaw calls the tools from the next message — no config files, and the Ipinfo.io key you paste is stored server-side instead of in your environment. ### How long does it take to connect Ipinfo.io to OpenClaw? About two minutes. Sign in, click Connect next to Ipinfo.io in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Ipinfo.io 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 Ipinfo.io working from chat. ### OpenClaw installed the Ipinfo.io skill but can't call the tools The ClawHub skill teaches OpenClaw about Ipinfo.io, but the calls run through the ClawLink plugin and your connected account. Make sure Ipinfo.io 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 - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/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.