ClawLink

How to connect Rkvst to Hermes Agent

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

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
Rkvst
Rkvst
RkvstAPI KEYMCP

DataTrails provides an evidence management platform that delivers a reliable chain of custody for supply chain data, ensuring data authenticity and transparency.. Once connected, Hermes Agent can read and act on Rkvst from chat — pairing, token refresh, and tool wiring handled for you.

24 tools

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

  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 Rkvst

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

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

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

Verify the connection by asking Hermes:

Use Rkvst to download event attachment and walk me through the result in plain English.

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

Rkvst MCP for Hermes

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

What the Hermes Agent Rkvst integration can do

24 Rkvst tools are ready for Hermes Agent once the account is connected.

All 24 Rkvst tools for Hermes

ToolWhat it does
Download event attachment rkvst_download_event_attachmentDownload an attachment from a specified Event on an Asset
Get app registration rkvst_get_app_registrationRetrieve details for a given App Registration ID
Get asset rkvst_get_assetRetrieve details for a given Asset
Get blob rkvst_get_blobRetrieve details of a Blob by ID
Get event rkvst_get_eventRetrieve details of a specified Event
Get iam subject rkvst_get_iam_subjectRetrieve IAM subject details
Get member rkvst_get_memberRetrieve details for a given Member ID
Get public asset rkvst_get_public_assetRetrieve details for a public asset
Get public asset event rkvst_get_public_asset_eventRetrieve a specific public asset event
Get tenancy rkvst_get_tenancyRetrieve details for a specific tenancy
List app registrations rkvst_list_app_registrationsList all App Registrations
List asset events rkvst_list_asset_eventsList events for a specified asset
List assets rkvst_list_assetsList all Assets with optional pagination and filters
List iam subjects rkvst_list_iam_subjectsList IAM subjects
List members rkvst_list_membersList all tenant Members
List public asset events rkvst_list_public_asset_eventsList events for a specific public asset
List public assets rkvst_list_public_assetsList all Public Assets
List tenancies rkvst_list_tenanciesList all tenancies
Retrieve asset attachment metadata rkvst_retrieve_asset_attachment_metadataRetrieve metadata for an attachment on a specified Asset
Retrieve caps rkvst_retrieve_capsRetrieve resource limit quotas for a specified service
Retrieve event attachment metadata rkvst_retrieve_event_attachment_metadataRetrieve metadata for an attachment on a specified Event
Search events rkvst_search_eventsSearch events matching filter criteria with pagination
Promote member rkvst_promote_memberPromote a tenant member to OWNER role
Update app registration rkvst_update_app_registrationUpdate an application's display name or custom claims

Try it: find the Rkvst tool you need

Browse the 24 Rkvst tools

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

Example prompts

Use Rkvst to download event attachment and walk me through the result in plain English.

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

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

Pull the relevant data from Rkvst, 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 Rkvst working from chat.

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

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

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

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

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

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

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

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

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

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

Hermes paired but still can't use Rkvst

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.