# How to connect Fireworks AI to OpenClaw (paste one key, 9 tools) > Connect Fireworks AI to OpenClaw with ClawLink: paste your Fireworks AI key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/fireworks-ai The usual route to Fireworks 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 Fireworks AI setup: install one ClawHub skill, connect Fireworks AI in the browser, and OpenClaw can call real Fireworks 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 Fireworks AI. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Fireworks AI** — 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 fireworks-ai # connect Fireworks AI (browser OAuth) npx -y @useclawlink/cli actions fireworks-ai # list available actions npx -y @useclawlink/cli run fireworks-ai --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 Fireworks AI in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fireworks AI API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Fireworks 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Fireworks AI is connected in the dashboard, that agent calls the same 9 Fireworks AI 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). ## Fireworks AI MCP for OpenClaw Looking for a Fireworks AI MCP server for OpenClaw? ClawLink connects Fireworks AI to OpenClaw and exposes 9 Fireworks AI 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 Fireworks AI integration](https://claw-link.dev/hermes/fireworks-ai) works the same way. ## What the OpenClaw Fireworks AI integration can do 9 Fireworks AI tools are ready for OpenClaw once the account is connected. ### All 9 Fireworks AI tools for OpenClaw | Tool | What it does | |---|---| | **Get deployment** `fireworks_ai_get_deployment` | Return configuration and serving status for one Fireworks deployment without scaling or | | **Get model** `fireworks_ai_get_model` | Return metadata and status for one model resource in a Fireworks account; this does not test | | **List accounts** `fireworks_ai_list_accounts` | Return one page of Fireworks accounts accessible to the API key so an agent can obtain account | | **List deployments** `fireworks_ai_list_deployments` | Return one page of deployment resources in a Fireworks account for deployment ID discovery and | | **List models** `fireworks_ai_list_models` | Return one page of model resources in a Fireworks account for model-ID discovery and status | | **Create chat completion** `fireworks_ai_create_chat_completion` | Generate one non-streaming OpenAI-compatible chat completion from role-based messages using a | | **Create embeddings** `fireworks_ai_create_embeddings` | Create embedding vectors for one or more caller-provided inputs using a caller-supplied | | **Generate model response** `fireworks_ai_generate_model_response` | Generate one non-streaming Responses API result, optionally continuing a stored response or | | **Rerank documents** `fireworks_ai_rerank_documents` | Rank a provided document list by relevance to a query using an optional caller-supplied | ## Example prompts **Get Deployment** > Pull the relevant data from Fireworks AI, summarize it in plain English, and point out anything that needs attention. **Get Model** > Pull the relevant data from Fireworks AI, summarize it in plain English, and point out anything that needs attention. **List Accounts** > List the relevant items in Fireworks AI, group them by priority, and recommend what OpenClaw should do next. **List Deployments** > List the relevant items in Fireworks AI, group them by priority, and recommend what OpenClaw should do next. ## 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 Fireworks AI working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Fireworks AI API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fireworks 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 Fireworks 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 Fireworks AI actions to the runtime in a format your agent can reliably use. | 9 tools for Fireworks AI are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Fireworks 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 Fireworks AI in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Fireworks AI 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 Fireworks AI skill but can't call the tools The ClawHub skill teaches OpenClaw about Fireworks AI, but the calls run through the ClawLink plugin and your connected account. Make sure Fireworks 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 Fireworks 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 Fireworks AI tools Fireworks 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 Fireworks 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. ### Fireworks 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 Fireworks AI has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Fireworks AI integration? Yes. ClawLink is the fastest way to connect OpenClaw to Fireworks AI: link your Fireworks AI account once in the browser and OpenClaw can call the Fireworks AI API through 9 ready-made tools — no custom code or token handling. ### How do I add Fireworks AI to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Fireworks AI skill from ClawHub, then you click Connect in the dashboard to authorize Fireworks AI. OpenClaw calls the tools from the next message — no config files, and the Fireworks AI key you paste is stored server-side instead of in your environment. ### How long does it take to connect Fireworks AI to OpenClaw? About two minutes. Sign in, click Connect next to Fireworks AI in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Fireworks 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 Fireworks AI working from chat. ### OpenClaw installed the Fireworks AI skill but can't call the tools The ClawHub skill teaches OpenClaw about Fireworks AI, but the calls run through the ClawLink plugin and your connected account. Make sure Fireworks 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 - [OpenClaw DataRobot integration](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. - [Connect 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.