# How to connect Kieai to OpenClaw (paste one key, 35 tools) > Connect Kieai to OpenClaw with ClawLink: paste your Kieai key once and 35 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/kieai The usual route to Kieai 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 Kieai setup: install one ClawHub skill, connect Kieai in the browser, and OpenClaw can call real Kieai 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 Kieai. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Kieai** — 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 kieai # connect Kieai (browser OAuth) npx -y @useclawlink/cli actions kieai # list available actions npx -y @useclawlink/cli run kieai --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 Kieai in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Kieai API key once. Verify the connection by asking OpenClaw: > Use Kieai to execute gpt codex 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 Kieai is connected in the dashboard, that agent calls the same 35 Kieai 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). ## Kieai MCP for OpenClaw Looking for a Kieai MCP server for OpenClaw? ClawLink connects Kieai to OpenClaw and exposes 35 Kieai 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 Kieai integration](https://claw-link.dev/hermes/kieai) works the same way. ## What the OpenClaw Kieai integration can do 35 Kieai tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 35. ### 30 of 35 Kieai tools for OpenClaw | Tool | What it does | |---|---| | **Execute gpt codex** `kieai_execute_gpt_codex` | Access GPT Codex capabilities through the KIE.AI Market API | | **Generate timestamped lyrics** `kieai_generate_timestamped_lyrics` | Retrieve synchronized lyrics with timestamps for a music track | | **Get account credits** `kieai_get_account_credits` | Retrieve the current credit balance for your KIE.AI account | | **Get aleph video details** `kieai_get_aleph_video_details` | Retrieves details and status of an Aleph video generation task | | **Get cover details** `kieai_get_cover_details` | Get the status and details of a cover song generation task | | **Get flux kontext image details** `kieai_get_flux_kontext_image_details` | Retrieve the status and details of a Flux Kontext image generation task | | **Get gpt4o image details** `kieai_get_gpt4o_image_details` | Retrieves details and status of a GPT-4o image generation task | | **Get lyrics details** `kieai_get_lyrics_details` | Retrieves the status and details of a lyrics generation task | | **Get market task details** `kieai_get_market_task_details` | Retrieves the status and details of a Market API task by its task ID | | **Get midi details** `kieai_get_midi_details` | Retrieves details and status of a MIDI generation task | | **Get music details** `kieai_get_music_details` | Get the status and details of a Suno music generation task including generated audio URLs and | | **Get music video details** `kieai_get_music_video_details` | Retrieves details and status of a music video generation task | | **Get runway video details** `kieai_get_runway_video_details` | Retrieves details and status of a Runway video generation task | | **Get timestamped lyrics status** `kieai_get_timestamped_lyrics_status` | Retrieve the status and results of a timestamped lyrics generation task | | **Get veo video details** `kieai_get_veo_video_details` | Retrieves details and status of a Veo3.1 video generation task | | **Get veo1080p video** `kieai_get_veo1080p_video` | Retrieve the 1080p high-definition version of a completed Veo3.1 video generation | | **Get veo4k video** `kieai_get_veo4k_video` | Retrieve the 4K ultra-high-definition version of a completed Veo3.1 video generation | | **Get wav details** `kieai_get_wav_details` | Retrieves the status and download URL for a WAV conversion task | | **Add instrumental** `kieai_add_instrumental` | Add AI-generated instrumental accompaniment to an existing vocal track | | **Add vocals** `kieai_add_vocals` | Add AI-generated vocals to an existing instrumental music track | | **Create market task** `kieai_create_market_task` | Create a task for unified model access through the Market API | | **Create music video** `kieai_create_music_video` | Create a music video (MP4) combining generated music with visuals | | **Extend music** `kieai_extend_music` | Extend an existing Suno music track with additional AI-generated content | | **Extend veo video** `kieai_extend_veo_video` | Extend an existing Veo3.1 video with additional AI-generated content | | **Generate aleph video** `kieai_generate_aleph_video` | Generate AI video using Runway Aleph model from text prompts | | **Generate cover** `kieai_generate_cover` | Generate a personalized cover version of a song using AI | | **Generate flux kontext image** `kieai_generate_flux_kontext_image` | Generate or edit images using the Flux Kontext model | | **Generate gpt4o image** `kieai_generate_gpt4o_image` | Generate images using the GPT-4o image generation model | | **Generate lyrics** `kieai_generate_lyrics` | Generate creative lyrics using AI | | **Generate midi** `kieai_generate_midi` | Generate MIDI file from audio or music generation | ## Example prompts **Execute Gpt Codex** > Use Kieai to execute gpt codex and walk me through the result in plain English. **Generate Timestamped Lyrics** > Use Kieai to generate timestamped lyrics and walk me through the result in plain English. **Get Account Credits** > Pull the relevant data from Kieai, summarize it in plain English, and point out anything that needs attention. **Get Aleph Video Details** > Pull the relevant data from Kieai, 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 Kieai working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Kieai API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Kieai 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 Kieai. | 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 Kieai actions to the runtime in a format your agent can reliably use. | 35 tools for Kieai are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Kieai 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 Kieai in the browser, and the 35 tools above work from chat. There is no SDK and no config file, and the Kieai 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 Kieai skill but can't call the tools The ClawHub skill teaches OpenClaw about Kieai, but the calls run through the ClawLink plugin and your connected account. Make sure Kieai 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 Kieai 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 Kieai tools Kieai 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 Kieai 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. ### Kieai 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 Kieai has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Kieai integration? Yes. ClawLink is the fastest way to connect OpenClaw to Kieai: link your Kieai account once in the browser and OpenClaw can call the Kieai API through 35 ready-made tools — no custom code or token handling. ### How do I add Kieai to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Kieai skill from ClawHub, then you click Connect in the dashboard to authorize Kieai. OpenClaw calls the tools from the next message — no config files, and the Kieai key you paste is stored server-side instead of in your environment. ### How long does it take to connect Kieai to OpenClaw? About two minutes. Sign in, click Connect next to Kieai in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Kieai 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 Kieai working from chat. ### OpenClaw installed the Kieai skill but can't call the tools The ClawHub skill teaches OpenClaw about Kieai, but the calls run through the ClawLink plugin and your connected account. Make sure Kieai 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](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. - [OpenClaw Chatbotkit integration](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. - [Just One API tools](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.