ClawLink

How to connect Openrouter to OpenClaw

Connect Openrouter to OpenClaw with ClawLink: paste your Openrouter key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Openrouter
Openrouter
OpenrouterAPI KEYMCP

OpenRouter is a platform that provides a unified API for accessing various large language models (LLMs) from different providers, allowing developers to integrate multiple AI models seamlessly.. Once connected, OpenClaw can read and act on Openrouter from chat — pairing, token refresh, and tool wiring handled for you.

13 tools

The usual route to Openrouter 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 Openrouter setup: install one ClawHub skill, connect Openrouter in the browser, and OpenClaw can call real Openrouter 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 Openrouter.

  1. 1

    Install 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. 2

    Connect Openrouter

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Openrouter?"

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-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 Openrouter in the ClawLink dashboard — paste your Openrouter API key once.

Verify the connection by asking OpenClaw:

Create it in Openrouter for me, then confirm the important fields before you finish.

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 login

login opens the same browser approval and stores a credential locally. Once Openrouter is connected in the dashboard, that agent calls the same 13 Openrouter tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Openrouter MCP for OpenClaw

Looking for a Openrouter MCP server for OpenClaw? ClawLink connects Openrouter to OpenClaw and exposes 13 Openrouter tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Openrouter integration works the same way.

What the OpenClaw Openrouter integration can do

13 Openrouter tools are ready for OpenClaw once the account is connected.

All 13 Openrouter tools for OpenClaw

ToolWhat it does
Create chat completion openrouter_create_chat_completionGenerate a chat-style completion
Create message openrouter_create_messageCreate a message using Anthropic Messages API format via OpenRouter
Get credits openrouter_get_creditsGet the current API credit balance for the authenticated user
Get current key openrouter_get_current_keyGet information about the currently authenticated API key
Get generation openrouter_get_generationRetrieve a generation result by its unique ID
Get models count openrouter_get_models_countGet the total count of available models on OpenRouter
List available models openrouter_list_available_modelsList available models via OpenRouter API
List embedding models openrouter_list_embedding_modelsList all available embeddings models via OpenRouter API
List model endpoints openrouter_list_model_endpointsList endpoints for a specific model
List providers openrouter_list_providersList all AI model providers available through the OpenRouter API
List user models openrouter_list_user_modelsList models filtered by user provider preferences, privacy settings, and guardrails
List zdr endpoints openrouter_list_zdr_endpointsPreview the impact of Zero Data Retention (ZDR) on the available endpoints
Create coinbase charge openrouter_create_coinbase_chargeCreate a Coinbase charge for crypto payment to add credits to your OpenRouter account

Try it: find the Openrouter tool you need

Browse the 13 Openrouter tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Create it in Openrouter for me, then confirm the important fields before you finish.

Create it in Openrouter for me, then confirm the important fields before you finish.

Pull the relevant data from Openrouter, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Openrouter, summarize it in plain English, and point out anything that needs attention.

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 Openrouter working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Openrouter API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Openrouter account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Openrouter.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Openrouter actions to the runtime in a format your agent can reliably use.13 tools for Openrouter are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Openrouter 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 Openrouter in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Openrouter 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 Openrouter skill but can't call the tools

The ClawHub skill teaches OpenClaw about Openrouter, but the calls run through the ClawLink plugin and your connected account. Make sure Openrouter 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 Openrouter 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 Openrouter tools

Openrouter 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 Openrouter 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.

Openrouter 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 Openrouter 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 Openrouter integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Openrouter: link your Openrouter account once in the browser and OpenClaw can call the Openrouter API through 13 ready-made tools — no custom code or token handling.

How do I add Openrouter to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Openrouter skill from ClawHub, then you click Connect in the dashboard to authorize Openrouter. OpenClaw calls the tools from the next message — no config files, and the Openrouter key you paste is stored server-side instead of in your environment.

How long does it take to connect Openrouter to OpenClaw?

About two minutes. Sign in, click Connect next to Openrouter in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Openrouter 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 Openrouter working from chat.

OpenClaw installed the Openrouter skill but can't call the tools

The ClawHub skill teaches OpenClaw about Openrouter, but the calls run through the ClawLink plugin and your connected account. Make sure Openrouter 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.