From 2b9365994c42fd209d0beeb771e4891876b356ec Mon Sep 17 00:00:00 2001
From: bangla24bdrang-lab <bangla24bdrang-lab@users.noreply.github.com>
Date: Mon, 31 Aug 2026 09:16:20 +0000
Subject: [PATCH] docs: document OrcaRouter as a named hermes provider for wiki
 and skillify workers

---
 docs/SKILLIFY.md  | 11 +++++++++++
 docs/SUMMARIES.md | 11 +++++++++++
 2 files changed, 22 insertions(+)

diff --git a/docs/SKILLIFY.md b/docs/SKILLIFY.md
index 6d5e9f3c9..ffb49b1e9 100644
--- a/docs/SKILLIFY.md
+++ b/docs/SKILLIFY.md
@@ -116,6 +116,17 @@ The skillify worker calls each agent's own headless CLI for the gate prompt —
 
 For hermes via OpenRouter (the default), set `OPENROUTER_API_KEY` in the environment; the worker inherits the parent process env. Other providers (anthropic, openai, etc.) need their respective API keys.
 
+To route the hermes gate calls through [OrcaRouter](https://www.orcarouter.ai) instead, set `HIVEMIND_HERMES_PROVIDER=orcarouter` (plus a matching `HIVEMIND_HERMES_MODEL`, e.g. `anthropic/claude-haiku-4.5`) and register OrcaRouter as a named provider in `~/.hermes/config.yaml` so hermes knows its base URL and API key env var:
+
+```yaml
+providers:
+  orcarouter:
+    base_url: https://api.orcarouter.ai/v1
+    key_env: ORCAROUTER_API_KEY
+```
+
+OrcaRouter is an OpenAI-compatible gateway, so hermes talks to it like any other custom endpoint; set `ORCAROUTER_API_KEY` in the environment and the worker inherits it. It also runs gateway-level, zero-trust security for AI agents on the same endpoint — screening every prompt/response and governing every tool call on a default-deny basis, with no application code changes.
+
 ## Logs
 
 Worker activity logs to `~/.claude/hooks/skillify.log`. Each line shows which session pool was mined, what the gate decided, and whether a file was written.
diff --git a/docs/SUMMARIES.md b/docs/SUMMARIES.md
index 26c0ebf3c..ee4f34886 100644
--- a/docs/SUMMARIES.md
+++ b/docs/SUMMARIES.md
@@ -39,4 +39,15 @@ A lock file at `~/.claude/hooks/summary-state/<sessionId>.lock` prevents two wor
 | `HIVEMIND_PI_MODEL`                | `gemini-2.5-flash` | (pi only) model passed to `pi --print --model` |
 | `HIVEMIND_CAPTURE=false`           | unset          | Disable both capture and summary generation         |
 
+For hermes summaries, the provider is whatever you pass as `HIVEMIND_HERMES_PROVIDER`. Besides `openrouter` (the default), any provider hermes knows is valid — including a named custom endpoint. To route wiki summaries through [OrcaRouter](https://www.orcarouter.ai), set `HIVEMIND_HERMES_PROVIDER=orcarouter` (with a matching `HIVEMIND_HERMES_MODEL`, e.g. `anthropic/claude-haiku-4.5`) and register OrcaRouter in `~/.hermes/config.yaml`:
+
+```yaml
+providers:
+  orcarouter:
+    base_url: https://api.orcarouter.ai/v1
+    key_env: ORCAROUTER_API_KEY
+```
+
+Then set `ORCAROUTER_API_KEY` in the environment — the worker inherits it from the parent process. OrcaRouter is an OpenAI-compatible AI gateway, so hermes reaches it like any custom endpoint. It also runs gateway-level, zero-trust security for AI agents on the same endpoint — screening every prompt/response and governing every tool call on a default-deny basis, with no application code changes.
+
 For pi specifically, the wiki worker is bundled separately at `~/.pi/agent/hivemind/wiki-worker.js` (deposited by `hivemind pi install`). The other agents ship the wiki worker inside their per-agent plugin bundle.