How to connect ImageRouter to OpenClaw
Connect ImageRouter to OpenClaw with ClawLink: paste your ImageRouter key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
ImageRouterAPI KEYMCPGenerate images, videos, and text with ImageRouter, inspect credits, validate normal API keys, and discover models.. Once connected, OpenClaw can read and act on ImageRouter from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to ImageRouter 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 ImageRouter setup: install one ClawHub skill, connect ImageRouter in the browser, and OpenClaw can call real ImageRouter 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 ImageRouter.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect ImageRouter
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with ImageRouter?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 ImageRouter in the ClawLink dashboard — paste your ImageRouter API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from ImageRouter, summarize it in plain English, and point out anything that needs attention.
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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once ImageRouter is connected in the dashboard, that agent calls the same 8 ImageRouter tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
ImageRouter MCP for OpenClaw
Looking for a ImageRouter MCP server for OpenClaw? ClawLink connects ImageRouter to OpenClaw and exposes 8 ImageRouter tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes ImageRouter integration works the same way.
What the OpenClaw ImageRouter integration can do
8 ImageRouter tools are ready for OpenClaw once the account is connected.
All 8 ImageRouter tools for OpenClaw
| Tool | What it does |
|---|---|
Get credits imagerouter_get_credits | Inspect remaining credits, cumulative usage, deposits, and optional per-key usage before making |
Get model imagerouter_get_model | Get current capabilities, accepted parameters, and pricing for one exact ImageRouter model ID |
List models imagerouter_list_models | Discover current ImageRouter model IDs, modalities, supported parameters, and pricing before |
Create chat completion imagerouter_create_chat_completion | Create a non-streaming OpenAI-compatible chat completion with a paid text model |
Create response imagerouter_create_response | Create a non-streaming OpenAI Responses API result from plain text or structured multimodal |
Edit image imagerouter_edit_image | Transform or inpaint one or more existing images supplied as URLs or data URIs |
Generate image imagerouter_generate_image | Generate an image from a text prompt with a selected ImageRouter model |
Generate video imagerouter_generate_video | Generate a video from text and optional URL or data-URI image inputs |
Try it: find the ImageRouter tool you need
Browse the 8 ImageRouter tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from ImageRouter, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from ImageRouter, summarize it in plain English, and point out anything that needs attention.
List the relevant items in ImageRouter, group them by priority, and recommend what OpenClaw should do next.
Create it in ImageRouter for me, then confirm the important fields before you finish.
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 ImageRouter working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the ImageRouter API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected ImageRouter 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 ImageRouter. | 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 ImageRouter actions to the runtime in a format your agent can reliably use. | 8 tools for ImageRouter are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes ImageRouter 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 ImageRouter in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the ImageRouter key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the ImageRouter skill but can't call the tools
The ClawHub skill teaches OpenClaw about ImageRouter, but the calls run through the ClawLink plugin and your connected account. Make sure ImageRouter 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 ImageRouter 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 ImageRouter tools
ImageRouter 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 ImageRouter 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.
ImageRouter 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 ImageRouter has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw ImageRouter integration?
Yes. ClawLink is the fastest way to connect OpenClaw to ImageRouter: link your ImageRouter account once in the browser and OpenClaw can call the ImageRouter API through 8 ready-made tools — no custom code or token handling.
How do I add ImageRouter to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink ImageRouter skill from ClawHub, then you click Connect in the dashboard to authorize ImageRouter. OpenClaw calls the tools from the next message — no config files, and the ImageRouter key you paste is stored server-side instead of in your environment.
How long does it take to connect ImageRouter to OpenClaw?
About two minutes. Sign in, click Connect next to ImageRouter in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring ImageRouter 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 ImageRouter working from chat.
OpenClaw installed the ImageRouter skill but can't call the tools
The ClawHub skill teaches OpenClaw about ImageRouter, but the calls run through the ClawLink plugin and your connected account. Make sure ImageRouter 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
Connect 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
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
OpenClaw Just One API integration
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.