Connect Hermes to AdKit

Hermes on your own machine. Sign in through the browser, no API key needed.

1. Install the CLI:

   npm i -g @adkit/cli
   

2. Sign in. This opens your browser to sign in to AdKit:

   adkit setup
   

3. Give Hermes this prompt to confirm the connection:

   Help me set up AdKit.
   
   1. Run `adkit status` to confirm AdKit is connected.
   2. Run `adkit checkin --agent hermes`.
   
   Tell me if AdKit is connected and ready. If not, tell me what failed.
   

On a server there is no browser to sign in with, so use an API key.

1. Create a key. Open Devices & Keys in AdKit and create an API key. It is shown once, so copy it right away.
2. Store the key in Hermes so it is injected into every run:

   hermes config set ADKIT_API_KEY adk_your_key
   

   
   This writes to ~/.hermes/.env. (Or set export ADKIT_API_KEY=adk_your_key in the service environment.)
3. Install the CLI:

   npm i -g @adkit/cli
   

4. Give Hermes this prompt to confirm the connection:

   Help me set up AdKit.
   
   1. Run `adkit status` to confirm AdKit is connected.
   2. Run `adkit checkin --agent hermes`.
   
   Tell me if AdKit is connected and ready. If not, tell me what failed.
   

Keep the key in the environment, not the chat. The CLI reads ADKIT_API_KEY from where Hermes runs, so the key never lands in your transcript.

Prefer MCP? Connect Hermes straight to AdKit, no proxy. Add this to ~/.hermes/config.yaml and replace adk_your_key:

mcp_servers:
  adkit:
    url: "https://mcp.adkit.so"
    headers:
      Authorization: "Bearer adk_your_key"