# How to connect Geoapify to OpenClaw (paste one key, 25 tools) > Connect Geoapify to OpenClaw with ClawLink: paste your Geoapify key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/geoapify The usual route to Geoapify 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 Geoapify setup: install one ClawHub skill, connect Geoapify in the browser, and OpenClaw can call real Geoapify 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 Geoapify. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Geoapify** — 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 geoapify # connect Geoapify (browser OAuth) npx -y @useclawlink/cli actions geoapify # list available actions npx -y @useclawlink/cli run geoapify --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 Geoapify in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Geoapify API key once. Verify the connection by asking OpenClaw: > Use Geoapify to address autocomplete 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 Geoapify is connected in the dashboard, that agent calls the same 25 Geoapify 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). ## Geoapify MCP for OpenClaw Looking for a Geoapify MCP server for OpenClaw? ClawLink connects Geoapify to OpenClaw and exposes 25 Geoapify 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 Geoapify integration](https://claw-link.dev/hermes/geoapify) works the same way. ## What the OpenClaw Geoapify integration can do 25 Geoapify tools are ready for OpenClaw once the account is connected. ### All 25 Geoapify tools for OpenClaw | Tool | What it does | |---|---| | **Address autocomplete** `geoapify_address_autocomplete` | Fetch address suggestions based on partial input | | **Boundaries** `geoapify_boundaries` | Retrieve all administrative boundaries that contain a given location | | **Forward geocoding** `geoapify_forward_geocoding` | Convert an address into geographic coordinates | | **Geometry** `geoapify_geometry` | Perform geometric operations on stored polygon geometries | | **Get batch forward geocode results** `geoapify_get_batch_forward_geocode_results` | Retrieve batch forward geocoding job results using the job ID | | **Get batch reverse geocode results** `geoapify_get_batch_reverse_geocode_results` | Retrieve batch reverse geocoding job results | | **Get boundaries consists of** `geoapify_get_boundaries_consists_of` | Get boundaries that a specified location consists of | | **Get map style** `geoapify_get_map_style` | Retrieve vector map style JSON for MapLibre GL and Mapbox GL | | **Get static map** `geoapify_get_static_map` | Generate static map images with customizable style, size, center, zoom, markers, and geometries | | **Ip geolocation** `geoapify_ip_geolocation` | Lookup geographic location information for an IP address | | **Isoline** `geoapify_isoline` | Generate isochrone or isodistance isolines | | **List postcodes** `geoapify_list_postcodes` | List postcodes within a specified area or boundary | | **Map matching** `geoapify_map_matching` | Snap GPS traces to the road network for accurate route reconstruction | | **Map tiles** `geoapify_map_tiles` | Fetch raster map tiles or style JSON from Geoapify | | **Marker icon** `geoapify_marker_icon` | Generate custom map marker icons as PNG images | | **Place details** `geoapify_place_details` | Retrieve detailed information about a specific place | | **Places** `geoapify_places` | Search for points of interest (POIs) like restaurants, hotels, attractions, hospitals, etc | | **Postcode** `geoapify_postcode` | Retrieve postcode information for a location | | **Reverse geocoding** `geoapify_reverse_geocoding` | Reverse geocode coordinates into a structured address | | **Route matrix** `geoapify_route_matrix` | Compute travel time and distance matrices | | **Route planner** `geoapify_route_planner` | Optimize multi-agent routes for deliveries, pickups, and service jobs | | **Routing** `geoapify_routing` | Calculate routes between multiple waypoints | | **Batch requests** `geoapify_batch_requests` | Create or retrieve asynchronous batch processing jobs for geocoding, reverse geocoding | | **Create batch forward geocode job** `geoapify_create_batch_forward_geocode_job` | Create a batch forward geocoding job for up to 1000 addresses | | **Create batch reverse geocode job** `geoapify_create_batch_reverse_geocode_job` | Create a batch reverse geocoding job that converts multiple lat/lon coordinates into addresses | ## Example prompts **Address Autocomplete** > Use Geoapify to address autocomplete and walk me through the result in plain English. **Boundaries** > Use Geoapify to boundaries and walk me through the result in plain English. **Forward Geocoding** > Use Geoapify to forward geocoding and walk me through the result in plain English. **Geometry** > Use Geoapify to geometry 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 Geoapify working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Geoapify API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Geoapify 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 Geoapify. | 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 Geoapify actions to the runtime in a format your agent can reliably use. | 25 tools for Geoapify are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Geoapify 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 Geoapify in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Geoapify 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 Geoapify skill but can't call the tools The ClawHub skill teaches OpenClaw about Geoapify, but the calls run through the ClawLink plugin and your connected account. Make sure Geoapify 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 Geoapify 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 Geoapify tools Geoapify 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 Geoapify 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. ### Geoapify 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 Geoapify has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Geoapify integration? Yes. ClawLink is the fastest way to connect OpenClaw to Geoapify: link your Geoapify account once in the browser and OpenClaw can call the Geoapify API through 25 ready-made tools — no custom code or token handling. ### How do I add Geoapify to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Geoapify skill from ClawHub, then you click Connect in the dashboard to authorize Geoapify. OpenClaw calls the tools from the next message — no config files, and the Geoapify key you paste is stored server-side instead of in your environment. ### How long does it take to connect Geoapify to OpenClaw? About two minutes. Sign in, click Connect next to Geoapify in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Geoapify 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 Geoapify working from chat. ### OpenClaw installed the Geoapify skill but can't call the tools The ClawHub skill teaches OpenClaw about Geoapify, but the calls run through the ClawLink plugin and your connected account. Make sure Geoapify 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 tools](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 - [Connect SafetyCulture](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.