How to connect Hyperise to Hermes Agent (paste one key, 5 tools)

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

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
Connect Hyperise
Paste your API key in the dashboard.
3
Use it from chat
Ask Hermes Agent: "What can you do with Hyperise?"

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

Verify the connection by asking Hermes:

List the relevant items in Hyperise, group them by priority, and recommend what Hermes should do next.

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

Hyperise MCP for Hermes

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

What the Hermes Agent Hyperise integration can do

5 Hyperise tools are ready for Hermes Agent once the account is connected.

All 5 Hyperise tools for Hermes

Tool	What it does
List image templates `hyperise_list_image_templates`	Retrieves all active personalized image templates for the authenticated user
User authentication `hyperise_user_authentication`	Authenticate an API token and retrieve user details
Create client account `hyperise_create_client_account`	Creates a new Hyperise business/client account for personalized image campaigns
Personalized short links `hyperise_personalized_short_links`	Generate a personalized short link with Open Graph metadata for rich link previews
Prospect business data `hyperise_prospect_business_data`	Perform CRUD operations on Hyperise business prospect records

Try it: find the Hyperise tool you need

Browse the 5 Hyperise tools

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

Example prompts

List the relevant items in Hyperise, group them by priority, and recommend what Hermes should do next.

Use Hyperise to user authentication and walk me through the result in plain English.

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

Use Hyperise to personalized short links and walk me through the result in plain English.

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

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

ClawLink vs. Composio

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

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

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

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

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

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

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

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

Why use ClawLink instead of wiring Hyperise up myself?

Hermes paired but still can't use Hyperise

How to connect Hyperise to Hermes Agent

Setup

Install and pair

Connect Hyperise

Use it from chat