# How to connect PromptLayer to OpenClaw (paste one key, 16 tools) > Connect PromptLayer to OpenClaw with ClawLink: paste your PromptLayer key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/promptlayer The usual route to PromptLayer 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 PromptLayer setup: install one ClawHub skill, connect PromptLayer in the browser, and OpenClaw can call real PromptLayer 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 PromptLayer. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect PromptLayer** — 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 promptlayer # connect PromptLayer (browser OAuth) npx -y @useclawlink/cli actions promptlayer # list available actions npx -y @useclawlink/cli run promptlayer --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 PromptLayer in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your PromptLayer API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from PromptLayer, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once PromptLayer is connected in the dashboard, that agent calls the same 16 PromptLayer 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). ## PromptLayer MCP for OpenClaw Looking for a PromptLayer MCP server for OpenClaw? ClawLink connects PromptLayer to OpenClaw and exposes 16 PromptLayer 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 PromptLayer integration](https://claw-link.dev/hermes/promptlayer) works the same way. ## What the OpenClaw PromptLayer integration can do 16 PromptLayer tools are ready for OpenClaw once the account is connected. ### All 16 PromptLayer tools for OpenClaw | Tool | What it does | |---|---| | **Get prompt template** `promptlayer_get_prompt_template` | Retrieve a prompt template version, release label, messages, model metadata, snippets, and | | **Get registered tool** `promptlayer_get_registered_tool` | Retrieve a PromptLayer registered tool definition by ID or name at a selected version or | | **Get request log** `promptlayer_get_request_log` | Retrieve one PromptLayer request log with its recorded input, output, timing, usage, metadata | | **Get skill collection** `promptlayer_get_skill_collection` | Retrieve a PromptLayer skill collection and its files as JSON at a selected version or release | | **Get table** `promptlayer_get_table` | Retrieve one PromptLayer Table's metadata and per-sheet row counts by UUID | | **Get workflow** `promptlayer_get_workflow` | Retrieve a PromptLayer workflow definition by ID or name at a specific version or release label | | **List folder entities** `promptlayer_list_folder_entities` | Browse or search PromptLayer folders and registry entities in the API-key workspace, optionally | | **List prompt templates** `promptlayer_list_prompt_templates` | Search and page through PromptLayer prompt templates and snippets without executing a model | | **List registered tools** `promptlayer_list_registered_tools` | List and filter tools defined in PromptLayer's tool registry without executing them | | **List skill collections** `promptlayer_list_skill_collections` | List and filter PromptLayer skill collections available in the API-key workspace | | **List table columns** `promptlayer_list_table_columns` | List one page of user and optionally system columns for a PromptLayer Table sheet | | **List table rows** `promptlayer_list_table_rows` | Read one page of rows and cells from a PromptLayer Table sheet, with optional schema and | | **List table sheets** `promptlayer_list_table_sheets` | List one page of sheets in a PromptLayer Table, optionally filtering by referenced prompt | | **List tables** `promptlayer_list_tables` | Search and page through PromptLayer Tables by folder, name, or referenced prompt | | **List workflows** `promptlayer_list_workflows` | Search and page through PromptLayer workflows without running them | | **Search request logs** `promptlayer_search_request_logs` | Search PromptLayer request logs by text or structured filters and return one rate-limited page | ## Example prompts **Get Prompt Template** > Pull the relevant data from PromptLayer, summarize it in plain English, and point out anything that needs attention. **Get Registered Tool** > Pull the relevant data from PromptLayer, summarize it in plain English, and point out anything that needs attention. **Get Request Log** > Pull the relevant data from PromptLayer, summarize it in plain English, and point out anything that needs attention. **Get Skill Collection** > Pull the relevant data from PromptLayer, 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 PromptLayer working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the PromptLayer API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PromptLayer 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 PromptLayer. | 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 PromptLayer actions to the runtime in a format your agent can reliably use. | 16 tools for PromptLayer are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PromptLayer 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 PromptLayer in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the PromptLayer 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 PromptLayer skill but can't call the tools The ClawHub skill teaches OpenClaw about PromptLayer, but the calls run through the ClawLink plugin and your connected account. Make sure PromptLayer 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 PromptLayer 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 PromptLayer tools PromptLayer 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 PromptLayer 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. ### PromptLayer 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 PromptLayer has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw PromptLayer integration? Yes. ClawLink is the fastest way to connect OpenClaw to PromptLayer: link your PromptLayer account once in the browser and OpenClaw can call the PromptLayer API through 16 ready-made tools — no custom code or token handling. ### How do I add PromptLayer to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink PromptLayer skill from ClawHub, then you click Connect in the dashboard to authorize PromptLayer. OpenClaw calls the tools from the next message — no config files, and the PromptLayer key you paste is stored server-side instead of in your environment. ### How long does it take to connect PromptLayer to OpenClaw? About two minutes. Sign in, click Connect next to PromptLayer in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring PromptLayer 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 PromptLayer working from chat. ### OpenClaw installed the PromptLayer skill but can't call the tools The ClawHub skill teaches OpenClaw about PromptLayer, but the calls run through the ClawLink plugin and your connected account. Make sure PromptLayer 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](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.