ClawLink

How to connect Openrouter to Hermes Agent

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

Get started for free
Hermes Agent
Hermes Agent
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, Hermes Agent can read and act on Openrouter from chat — pairing, token refresh, and tool wiring handled for you.

122 tools

Most guides for giving Hermes Agent Openrouter access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Openrouter setup: pair once in the browser and your always-on Hermes agent can act on Openrouter for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Hermes to Openrouter.

  1. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect Openrouter

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with Openrouter?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect Openrouter in the ClawLink dashboard — paste your Openrouter API key once.

Verify the connection by asking Hermes:

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

Using a different agent?

The Hermes 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 122 Openrouter tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Openrouter MCP for Hermes

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

What the Hermes Agent Openrouter integration can do

122 Openrouter tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 122.

30 of 122 Openrouter tools for Hermes

ToolWhat it does
Create transcription openrouter_create_transcriptionTranscribe audio into text using an OpenRouter speech-to-text model
Download container file content openrouter_download_container_file_contentDownload raw file content from an OpenRouter container using its canonical container and file
Download file content openrouter_download_file_contentDownload raw content of a server-created file
Get analytics meta openrouter_get_analytics_metaReturns the available metrics, dimensions, filter operators, and granularities for the
Get API key openrouter_get_api_keyGet a single API key by hash
Get app rankings openrouter_get_app_rankingsReturns the top public apps on OpenRouter ranked by token usage inside the requested date
Get batch openrouter_get_batchReturns a batch with its status and request counts
Get benchmarks openrouter_get_benchmarksUnified benchmark endpoint that aggregates scores from multiple benchmark sources (Artificial
Get byok credential openrouter_get_byok_credentialGet a single bring-your-own-key (BYOK) provider credential by its id
Get container file openrouter_get_container_fileReturns the metadata of a single file in a container
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 file metadata openrouter_get_file_metadataRetrieves metadata for a single file owned by the requesting workspace
Get generation openrouter_get_generationRetrieve a generation result by its unique ID
Get guardrail openrouter_get_guardrailGet a single guardrail by ID
Get model openrouter_get_modelReturns full details for a single model identified by its author and slug (e.g
Get models count openrouter_get_models_countGet the total count of available models on OpenRouter
Get oauth signing keys openrouter_get_oauth_signing_keysRFC 7517 JWK Set containing the public keys OpenRouter signs access tokens with
Get observability destination openrouter_get_observability_destinationFetch a single observability destination by its UUID
Get organization settings openrouter_get_organization_settingsGet the settings of the organization associated with the authenticated management key
Get preset openrouter_get_presetRetrieves a preset by its slug with its currently designated version inline
Get preset version openrouter_get_preset_versionRetrieves a specific version of a preset by its slug and version number
Get private endpoint openrouter_get_private_endpointGet one private endpoint with its upstream configuration and current pricing
Get rankings daily openrouter_get_rankings_dailyReturns the top 50 public models per day by total token usage on OpenRouter, plus a single
Get scim group mapping openrouter_get_scim_group_mappingGet a SCIM group-to-workspace mapping
Get scim sync job openrouter_get_scim_sync_jobGet SCIM directory sync status
Get session cost openrouter_get_session_costReturns weekly refreshed, aggregated cost-per-session cells for the published harnesses
Get task classifications openrouter_get_task_classificationsReturns the market-share breakdown of OpenRouter traffic by task classification (e.g
Get tool openrouter_get_toolOne server tool by canonical name or any accepted alias, with the models that run it natively
Get user activity openrouter_get_user_activityReturns user activity data grouped by endpoint for the last 30 (completed) UTC days

Try it: find the Openrouter tool you need

Browse the 30 Openrouter tools

Click any tool to see exactly what Hermes 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.

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. 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.122 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 Hermes Agent users instead. You install the plugin once, connect Openrouter in the browser, and the 122 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

Hermes paired but still can't use Openrouter

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

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

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

How do I connect Openrouter to Hermes with ClawLink?

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Openrouter in the dashboard and Hermes can use it 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 Hermes Agent?

About two minutes. Sign in, click Connect next to Openrouter in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Openrouter working from chat.

Hermes paired but still can't use Openrouter

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

On this page