ClawLink

How to connect OpenRegister to Hermes Agent

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

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
OpenRegister
OpenRegister
OpenRegisterAPI KEYMCP

OpenRegister provides structured German company, person, ownership, financial, insolvency, document, monitoring, and usage data.. Once connected, Hermes Agent can read and act on OpenRegister from chat — pairing, token refresh, and tool wiring handled for you.

10 tools

Most guides for giving Hermes Agent OpenRegister 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 OpenRegister setup: pair once in the browser and your always-on Hermes agent can act on OpenRegister 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 OpenRegister.

  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 OpenRegister

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

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

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

Verify the connection by asking Hermes:

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

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 OpenRegister is connected in the dashboard, that agent calls the same 10 OpenRegister tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

OpenRegister MCP for Hermes

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

What the Hermes Agent OpenRegister integration can do

10 OpenRegister tools are ready for Hermes Agent once the account is connected.

All 10 OpenRegister tools for Hermes

ToolWhat it does
Get company data open_register_get_company_dataRead one company profile, financials, historical ownership, holdings, current owners, or UBOs
Get credit usage open_register_get_credit_usageCheck the connected OpenRegister account's plan, included and used credits, remaining balance
Get document open_register_get_documentFetch an official Handelsregister document in real time for a company or retrieve a stored
Get insolvency open_register_get_insolvencyGet one insolvency proceeding and its complete published event history, including linked
Get person data open_register_get_person_dataRead a person's profile and management positions or the companies in which they hold ownership
List monitors open_register_list_monitorsList every company and person monitor for the connected OpenRegister account, including
Lookup company by URL open_register_lookup_company_by_urlResolve a fully qualified company website URL to its OpenRegister company ID and available
Search companies open_register_search_companiesFind companies by name or structured criteria
Search insolvencies open_register_search_insolvenciesSearch German insolvency proceedings by free text or structured debtor, proceeding, status
Search people open_register_search_peopleSearch natural persons by name, birth date, city, or active status

Try it: find the OpenRegister tool you need

Browse the 10 OpenRegister tools

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

Example prompts

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

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

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

Pull the relevant data from OpenRegister, 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want OpenRegister working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the OpenRegister API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected OpenRegister 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 OpenRegister.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 OpenRegister actions to the runtime in a format your agent can reliably use.10 tools for OpenRegister are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes OpenRegister 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 OpenRegister in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the OpenRegister 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 OpenRegister

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 OpenRegister 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 OpenRegister tools

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

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

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

How do I connect OpenRegister 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 OpenRegister in the dashboard and Hermes can use it from the next message — no config files, and the OpenRegister key you paste is stored server-side instead of in your environment.

How long does it take to connect OpenRegister to Hermes Agent?

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

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

Hermes paired but still can't use OpenRegister

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.