How to connect Inworld AI to OpenClaw
Connect Inworld AI to OpenClaw with ClawLink: paste your Inworld AI key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
Inworld AIAPI KEYMCPInworld AI provides native APIs for speech synthesis, speech recognition, voice management, model discovery, embeddings, knowledge, and router management.. Once connected, OpenClaw can read and act on Inworld AI from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Inworld AI 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 Inworld AI setup: install one ClawHub skill, connect Inworld AI in the browser, and OpenClaw can call real Inworld AI 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 Inworld AI.
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 Inworld AI
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Inworld AI?"
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 Inworld AI in the ClawLink dashboard — paste your Inworld AI API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Inworld AI, 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 Inworld AI is connected in the dashboard, that agent calls the same 6 Inworld AI tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Inworld AI MCP for OpenClaw
Looking for a Inworld AI MCP server for OpenClaw? ClawLink connects Inworld AI to OpenClaw and exposes 6 Inworld AI tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Inworld AI integration works the same way.
What the OpenClaw Inworld AI integration can do
6 Inworld AI tools are ready for OpenClaw once the account is connected.
All 6 Inworld AI tools for OpenClaw
| Tool | What it does |
|---|---|
Get voice preview inworld_ai_get_voice_preview | Generate the provider-selected, unmetered MP3 preview for a voice and return it as a |
List models inworld_ai_list_models | List Inworld-supported models and the pricing, modality, context, and output limits needed to |
List voices inworld_ai_list_voices | Return one page of voices available for preview or speech synthesis, with optional filtering |
Create embeddings inworld_ai_create_embeddings | Generate one complete embedding vector per input text with an Inworld-hosted embedding model |
Synthesize speech inworld_ai_synthesize_speech | Synthesize short text with an Inworld voice and return the complete audio as a downloadable file |
Transcribe audio inworld_ai_transcribe_audio | Synchronously transcribe a short audio file and return the final transcript, timestamps, and |
Try it: find the Inworld AI tool you need
Browse the 6 Inworld AI 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 Inworld AI, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Inworld AI, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Inworld AI, group them by priority, and recommend what OpenClaw should do next.
Create it in Inworld AI 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 Inworld AI working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Inworld AI API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Inworld AI 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 Inworld AI. | 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 Inworld AI actions to the runtime in a format your agent can reliably use. | 6 tools for Inworld AI are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Inworld AI 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 Inworld AI in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Inworld AI 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 Inworld AI skill but can't call the tools
The ClawHub skill teaches OpenClaw about Inworld AI, but the calls run through the ClawLink plugin and your connected account. Make sure Inworld AI 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 Inworld AI 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 Inworld AI tools
Inworld AI 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 Inworld AI 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.
Inworld AI 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 Inworld AI 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 Inworld AI integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Inworld AI: link your Inworld AI account once in the browser and OpenClaw can call the Inworld AI API through 6 ready-made tools — no custom code or token handling.
How do I add Inworld AI to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Inworld AI skill from ClawHub, then you click Connect in the dashboard to authorize Inworld AI. OpenClaw calls the tools from the next message — no config files, and the Inworld AI key you paste is stored server-side instead of in your environment.
How long does it take to connect Inworld AI to OpenClaw?
About two minutes. Sign in, click Connect next to Inworld AI in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Inworld AI 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 Inworld AI working from chat.
OpenClaw installed the Inworld AI skill but can't call the tools
The ClawHub skill teaches OpenClaw about Inworld AI, but the calls run through the ClawLink plugin and your connected account. Make sure Inworld AI 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
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
Connect 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.
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.