How to connect Hostinger to Hermes Agent

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.

Reconnect Hostinger from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

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

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.

The AIO teaches formatting Authorization: Bearer YOUR_API_TOKEN exactly, with the token case-sensitive and free of stray spaces, and that tokens are generated in hPanel under Account Information. On a hosted connection there is no header for you to format and no local file to check, so a 401 means the stored token itself is the problem: it was revoked in hPanel, it was pasted with surrounding whitespace, or it belongs to a different Hostinger account. Reconnect Hostinger from the ClawLink dashboard with a fresh token generated in the right hPanel account, and confirm the key was copied without extra characters. A 401 that persists across a fresh token is worth raising with support, because nothing on the agent side can format this request differently.

Hostinger applies API rate limits to the account, and a hosted connection shares them because the calls run under your token. When a tool returns 429, the agent should stop and retry later rather than hammering the endpoint; repeating the request immediately makes the window longer. Reconnecting does not reset the account's limits. If the agent is looping on a call, tell it to back off and continue with other work.

The query space answers this with local fixes: the hostinger-api-mcp binary missing from PATH, a wrong config directory, or a reinstall with npm i -g hostinger-api-mcp. None of that exists on a hosted connection, because there is no binary and no PATH to check. If a Hostinger tool is missing from your agent's catalog, the cause is on the catalog side: reconnect Hostinger from the dashboard, then start a fresh chat so the runtime reloads the tool list. If you are running the npm package yourself and hit these errors, that is the install path, not this connection.

Double-check that the API key for Hostinger has the right scopes or account access. A valid key can still be too limited for some reads or writes.

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

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

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

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

No. The AI Overviews for Hostinger MCP teach npm install -g hostinger-api-mcp, which requires Node.js 24 or higher and exposes the full 276-tool catalog from Hostinger's own README, or the modular packages like hostinger-hosting-mcp (48 tools) and hostinger-vps-mcp (62 tools). ClawLink skips the installation entirely: you paste a Hostinger API token once, and 24 curated tools are available to Hermes from chat. You keep the full API for anything the curated set does not cover; this is for the agent-facing actions people actually use.

Hostinger's product installs and runs the Hermes Agent itself on one of their VPS servers, with admin credentials you set in the setup wizard. This page does not do that. Here, Hermes runs anywhere you already run it, and Hostinger is a connected tool: the agent can check domain availability, read and validate DNS records, list VPS machines and websites, and manage SSH keys on your account. If you came to deploy the agent, you want Hostinger's catalog installation; if you came to give an existing agent Hostinger access, this is the page.

The risk discussion in the ecosystem is about over-privileged access, and the practical version for this connection is simple: the token you paste is an API token for your Hostinger account, so it carries the account's scope. You can revoke or rotate it in hPanel at any time, and ClawLink stores it server-side rather than in a file on the machine running Hermes. Treat the connection like the account credential it is, and disconnect it from the dashboard when you stop using it.

Hostinger sells its own no-API-key story: a built-in AI assistant billed through credits you buy in the hPanel dashboard, and a one-click OpenClaw deployment. Those live inside Hostinger's control panel and are not an API surface an external runtime like Hermes can call. If you want a Hermes agent that manages domains, DNS, and VPS resources itself, it needs the API token connection this page describes.

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.