# How to connect Explorium to OpenClaw (paste one key, 10 tools) > Connect Explorium to OpenClaw with ClawLink: paste your Explorium key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/explorium The usual route to Explorium 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 Explorium setup: install one ClawHub skill, connect Explorium in the browser, and OpenClaw can call real Explorium 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 Explorium. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Explorium** — 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 explorium # connect Explorium (browser OAuth) npx -y @useclawlink/cli actions explorium # list available actions npx -y @useclawlink/cli run explorium --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 Explorium in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Explorium API key once. Verify the connection by asking OpenClaw: > Use Explorium to autocomplete filter values 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 Explorium is connected in the dashboard, that agent calls the same 10 Explorium 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). ## Explorium MCP for OpenClaw Looking for a Explorium MCP server for OpenClaw? ClawLink connects Explorium to OpenClaw and exposes 10 Explorium 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 Explorium integration](https://claw-link.dev/hermes/explorium) works the same way. ## What the OpenClaw Explorium integration can do 10 Explorium tools are ready for OpenClaw once the account is connected. ### All 10 Explorium tools for OpenClaw | Tool | What it does | |---|---| | **Autocomplete filter values** `explorium_autocomplete_filter_values` | Find normalized values for Explorium business and prospect search filters, including company | | **Enrich business firmographics** `explorium_enrich_business_firmographics` | Enrich 1-50 Explorium business IDs with company firmographics | | **Get audience stats** `explorium_get_audience_stats` | Return aggregate distributions and total counts for either a business or prospect filter set | | **Get credit balance** `explorium_get_credit_balance` | Return the connected Explorium company's allocated and remaining credits and trial or paid | | **Get job status** `explorium_get_job_status` | Get detailed status, timing, credit usage, errors, and downloadable CSV result metadata for one | | **List jobs** `explorium_list_jobs` | List existing Explorium asynchronous jobs, optionally filtered by lifecycle status, and return | | **Match businesses** `explorium_match_businesses` | Resolve 1-50 business names, domains, URLs, or LinkedIn URLs to Explorium business IDs while | | **Match prospects** `explorium_match_prospects` | Resolve 1-50 people from names, employers, email, phone, LinkedIn URL, or Explorium business ID | | **Search businesses** `explorium_search_businesses` | Search Explorium businesses with structured filters and cursor pagination | | **Search prospects** `explorium_search_prospects` | Search Explorium prospects with strict person and employer filters, returning one | ## Example prompts **Autocomplete Filter Values** > Use Explorium to autocomplete filter values and walk me through the result in plain English. **Enrich Business Firmographics** > Use Explorium to enrich business firmographics and walk me through the result in plain English. **Get Audience Stats** > Pull the relevant data from Explorium, summarize it in plain English, and point out anything that needs attention. **Get Credit Balance** > Pull the relevant data from Explorium, 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 Explorium working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Explorium API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Explorium 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 Explorium. | 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 Explorium actions to the runtime in a format your agent can reliably use. | 10 tools for Explorium are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Explorium 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 Explorium in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Explorium 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 Explorium skill but can't call the tools The ClawHub skill teaches OpenClaw about Explorium, but the calls run through the ClawLink plugin and your connected account. Make sure Explorium 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 Explorium 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 Explorium tools Explorium 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 Explorium 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. ### Explorium 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 Explorium has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Explorium integration? Yes. ClawLink is the fastest way to connect OpenClaw to Explorium: link your Explorium account once in the browser and OpenClaw can call the Explorium API through 10 ready-made tools — no custom code or token handling. ### How do I add Explorium to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Explorium skill from ClawHub, then you click Connect in the dashboard to authorize Explorium. OpenClaw calls the tools from the next message — no config files, and the Explorium key you paste is stored server-side instead of in your environment. ### How long does it take to connect Explorium to OpenClaw? About two minutes. Sign in, click Connect next to Explorium in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Explorium 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 Explorium working from chat. ### OpenClaw installed the Explorium skill but can't call the tools The ClawHub skill teaches OpenClaw about Explorium, but the calls run through the ClawLink plugin and your connected account. Make sure Explorium 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 - [DataRobot tools](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Connect Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.