# How to connect Studio By Ai21 Labs to OpenClaw (paste one key, 57 tools) > Connect Studio By Ai21 Labs to OpenClaw with ClawLink: paste your Studio By Ai21 Labs key once and 57 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/studio-by-ai21-labs The usual route to Studio By Ai21 Labs 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 Studio By Ai21 Labs setup: install one ClawHub skill, connect Studio By Ai21 Labs in the browser, and OpenClaw can call real Studio By Ai21 Labs 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 Studio By Ai21 Labs. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Studio By Ai21 Labs** — 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 studio-by-ai21-labs # connect Studio By Ai21 Labs (browser OAuth) npx -y @useclawlink/cli actions studio-by-ai21-labs # list available actions npx -y @useclawlink/cli run studio-by-ai21-labs --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 Studio By Ai21 Labs in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Studio By Ai21 Labs API key once. Verify the connection by asking OpenClaw: > Use Studio By Ai21 Labs to check can iframe 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 Studio By Ai21 Labs is connected in the dashboard, that agent calls the same 57 Studio By Ai21 Labs 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). ## Studio By Ai21 Labs MCP for OpenClaw Looking for a Studio By Ai21 Labs MCP server for OpenClaw? ClawLink connects Studio By Ai21 Labs to OpenClaw and exposes 57 Studio By Ai21 Labs 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 Studio By Ai21 Labs integration](https://claw-link.dev/hermes/studio-by-ai21-labs) works the same way. ## What the OpenClaw Studio By Ai21 Labs integration can do 57 Studio By Ai21 Labs 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 57. ### 30 of 57 Studio By Ai21 Labs tools for OpenClaw | Tool | What it does | |---|---| | **Check can iframe** `studio_by_ai21_labs_check_can_iframe` | Check if a URL can be embedded in an iframe | | **Compare text** `studio_by_ai21_labs_compare_text` | Compare two text strings and identify differences | | **Create generation requirements** `studio_by_ai21_labs_create_generation_requirements` | Generate requirements from a query or task description | | **Create generation thread name** `studio_by_ai21_labs_create_generation_thread_name` | Generate a thread name from a query or conversation context | | **Create kirsh grant compliance preview** `studio_by_ai21_labs_create_kirsh_grant_compliance_preview` | Preview grant compliance for Kirsh grants | | **Create kirsh grant preview** `studio_by_ai21_labs_create_kirsh_grant_preview` | Retrieve grant metadata from the Kirsh preview endpoint | | **Create solutions kirsh grant compliance** `studio_by_ai21_labs_create_solutions_kirsh_grant_compliance` | Check compliance for Kirsh grant IDs | | **Download modified document** `studio_by_ai21_labs_download_modified_document` | Download a modified document from AI21 Labs Studio | | **Get assistant** `studio_by_ai21_labs_get_assistant` | Retrieve an assistant by its unique identifier | | **Get assistant route** `studio_by_ai21_labs_get_assistant_route` | Retrieve details of a specific route for an AI21 Studio assistant | | **Get assistants by mcp** `studio_by_ai21_labs_get_assistants_by_mcp` | Retrieve all assistants associated with a specific MCP (Model Context Protocol) storage | | **Get batch status** `studio_by_ai21_labs_get_batch_status` | Check the status of a Fnac Aftersales parts classification batch prediction job | | **Get demo** `studio_by_ai21_labs_get_demo` | Retrieve a demo by its unique ID | | **Get kirsh grant metadata** `studio_by_ai21_labs_get_kirsh_grant_metadata` | Retrieve Kirsh grant metadata by grant ID | | **Get library batch status** `studio_by_ai21_labs_get_library_batch_status` | Get the ingestion status of a library batch | | **Get mcp storage** `studio_by_ai21_labs_get_mcp_storage` | Retrieve a specific MCP (Model Context Protocol) storage configuration by its unique ID | | **Get output explanation** `studio_by_ai21_labs_get_output_explanation` | Get output explanation for an execution (cached or generated) | | **Get plan** `studio_by_ai21_labs_get_plan` | Retrieve a specific plan from an AI21 Studio assistant | | **Get website connector by ID** `studio_by_ai21_labs_get_website_connector_by_id` | Retrieve details of a specific website connector by its ID | | **Get website connector status** `studio_by_ai21_labs_get_website_connector_status` | Retrieve the status of a website connector ingestion | | **Get website connector URL status** `studio_by_ai21_labs_get_website_connector_url_status` | Retrieve the status of a specific URL in the website connector | | **List assistants** `studio_by_ai21_labs_list_assistants` | Retrieve all assistants from AI21 Studio | | **List connectors website** `studio_by_ai21_labs_list_connectors_website` | Retrieve website connector information from AI21 Studio | | **List demos** `studio_by_ai21_labs_list_demos` | Retrieve all demos from AI21 Studio | | **List library files** `studio_by_ai21_labs_list_library_files` | List files in the workspace library with optional filtering | | **List mcp storage** `studio_by_ai21_labs_list_mcp_storage` | Retrieve all MCP (Model Context Protocol) storage configurations from AI21 Studio | | **List models** `studio_by_ai21_labs_list_models` | Retrieve information about all available AI21 models | | **List plans** `studio_by_ai21_labs_list_plans` | List all plans for a specific assistant | | **List secrets** `studio_by_ai21_labs_list_secrets` | Retrieve all secrets from AI21 Studio secret storage | | **List settings models** `studio_by_ai21_labs_list_settings_models` | Retrieve all workspace models by organization from AI21 Studio | ## Example prompts **Check Can Iframe** > Use Studio By Ai21 Labs to check can iframe and walk me through the result in plain English. **Compare Text** > Use Studio By Ai21 Labs to compare text and walk me through the result in plain English. **Create Generation Requirements** > Create it in Studio By Ai21 Labs for me, then confirm the important fields before you finish. **Create Generation Thread Name** > Create it in Studio By Ai21 Labs 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 Studio By Ai21 Labs working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Studio By Ai21 Labs API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Studio By Ai21 Labs 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 Studio By Ai21 Labs. | 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 Studio By Ai21 Labs actions to the runtime in a format your agent can reliably use. | 57 tools for Studio By Ai21 Labs are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Studio By Ai21 Labs 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 Studio By Ai21 Labs in the browser, and the 57 tools above work from chat. There is no SDK and no config file, and the Studio By Ai21 Labs 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 Studio By Ai21 Labs skill but can't call the tools The ClawHub skill teaches OpenClaw about Studio By Ai21 Labs, but the calls run through the ClawLink plugin and your connected account. Make sure Studio By Ai21 Labs 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 Studio By Ai21 Labs 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 Studio By Ai21 Labs tools Studio By Ai21 Labs 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 Studio By Ai21 Labs 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. ### Studio By Ai21 Labs 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 Studio By Ai21 Labs has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Studio By Ai21 Labs integration? Yes. ClawLink is the fastest way to connect OpenClaw to Studio By Ai21 Labs: link your Studio By Ai21 Labs account once in the browser and OpenClaw can call the Studio By Ai21 Labs API through 57 ready-made tools — no custom code or token handling. ### How do I add Studio By Ai21 Labs to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Studio By Ai21 Labs skill from ClawHub, then you click Connect in the dashboard to authorize Studio By Ai21 Labs. OpenClaw calls the tools from the next message — no config files, and the Studio By Ai21 Labs key you paste is stored server-side instead of in your environment. ### How long does it take to connect Studio By Ai21 Labs to OpenClaw? About two minutes. Sign in, click Connect next to Studio By Ai21 Labs in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Studio By Ai21 Labs 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 Studio By Ai21 Labs working from chat. ### OpenClaw installed the Studio By Ai21 Labs skill but can't call the tools The ClawHub skill teaches OpenClaw about Studio By Ai21 Labs, but the calls run through the ClawLink plugin and your connected account. Make sure Studio By Ai21 Labs 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. - [Chatbotkit](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.