SPACE ROUTER · Hermes Agent
Hermes Agent + Space Router
Install Hermes, choose a custom endpoint and protocol, then test chat and tool access before real work.
Before you start
| Field | Value | Check |
|---|---|---|
| Supported setup | Windows; macOS on Apple Silicon | Choose the matching OS installer; keep your current configuration backup |
| Account | A Space Router account and matching group credit/subscription | The app’s own login and the router API key are separate |
Download stages are shown in the terminal. Direct downloads show a progress bar or received bytes; package managers use their own output. A percentage may be unavailable. Keep the terminal open until the final installation and connection results.
Space Router one-click scripts report INSTALLATION separately from CONNECTION. DONE means the app or command was checked; VERIFIED means the stated response test passed. SKIPPED / NOT CONFIGURED needs the connection steps. FAILED / INCOMPLETE needs the displayed error fixed. A CLI test does not verify a desktop app or editor panel.
Model examples and placeholders must be replaced with IDs allowed by your key’s group. You can install the app first, then create the key before the connection steps.
When this tool uses your Space Router endpoint and key, its model requests use your Space Router balance or eligible subscription. App sign-in, app subscriptions and cloud-only features are separate. Confirm the actual route in usage history after testing.
1 · One-click installation
Choose the packaged desktop app if you want the simplest first install, or use the official CLI script below. Source installation may download runtimes and optional browser tools; it is more than a provider-setting change.
Windows
Open the PowerShell app: press the Windows key, type PowerShell, and open it. Copy the command below, paste it into PowerShell, then press Enter.
iex (irm https://stationine.com/setup-hermes.ps1)The official site provides a Windows desktop package. Open its appinstaller with Windows App Installer, or use the native PowerShell CLI installer:
macOS
Open the Terminal app: press Command + Space, type Terminal, and open it. Copy the command below, paste it into Terminal, then press Return.
bash -c 'script=$(curl -fL --progress-bar https://stationine.com/setup-hermes.sh) && test -n "$script" && bash -c "$script"'Current official macOS support is Apple Silicon; Intel Macs are not supported by the current installer. Download the Mac desktop package and move Hermes to Applications, or use the CLI script on a supported Mac:
Let installation finish, reopen your shell and check:
hermes --help
hermes doctorYou should see the CLI help and diagnostics. For the initial setup, skip optional messaging integrations until the model connection works.
2 · Create your API key
Sign in to Space Router
Open space.stationine.com and sign in to your own account. Confirm you have usable credit or an eligible subscription before testing.Create a dedicated API key
Open API Keys → Create API Key. Name the key after this tool. Select GPT / OpenAI or Claude / Anthropic; use the groups actually available to your account. A key for a different model family is not interchangeable.Copy the full key and the model ID
Save the full key in your password manager. Copy one exact model ID allowed by that key’s group from Available Channels. Keep any limits or expiry you need. A model shown in an app’s public list may not belong to your key.Keep the key private
Paste the key only into your own app or local credential store. Do not include it in shared screenshots, project files, import links or support messages. For two purchased groups, create two separate keys.

3 · Connect Space Router
Quick start: interactive model selection
Open the model selector
Runhermes model. Choose a custom endpoint rather than the built-in OpenRouter provider. If the provider is missing, add its credential in the picker’s Keys area.Match URL, protocol, key and model
For GPT use https://space.stationine.com/v1 and Chat Completions. For Claude use https://space.stationine.com and Anthropic Messages. Enter the matching group key and exact model ID, save, then start a new chat.
Manual configuration and diagnostics
Start with hermes model if you prefer the interactive provider picker. Choose a custom endpoint and enter the matching key, URL, model and protocol. For a file-based setup, use the path printed below; do not assume the same default directory on all platforms.
hermes config path
hermes config env-path
hermes config editIn the opened private configuration, merge one matching model block. The key below is a placeholder; keep the actual file private. A current native Windows install commonly uses its LocalAppData data directory, while a POSIX install commonly uses ~/.hermes; HERMES_HOME can override either.
GPT · OpenAI Chat Completions
model:
provider: custom
base_url: https://space.stationine.com/v1
api_mode: chat_completions
api_key: YOUR_GPT_GROUP_KEY
default: YOUR_GPT_MODEL_IDClaude · Anthropic Messages
model:
provider: custom
base_url: https://space.stationine.com
api_mode: anthropic_messages
api_key: YOUR_CLAUDE_GROUP_KEY
default: YOUR_CLAUDE_MODEL_IDThese two panels are alternatives by API format, not operating system. Replace all placeholders and choose one block. When switching groups, change the protocol and credential together; do not leave an old Anthropic mode on a GPT endpoint. Reopen Hermes and use hermes config check before chatting.
4 · Verify a real response
Reopen the client
Save your settings, fully quit the app and reopen it. Start a new conversation. Select the Space Router provider and the exact model allowed by your key; do not leave the previous provider selected.Ask a small, checkable question
SendWhat is 17 plus 25? Reply with just the number.Expect a complete reply of42. This uses your account credit at the selected model’s normal rate. A speed check or HTTP 200 alone is not enough.Match the usage record
Open Space Router’s usage history. Match the request time, model and API key with this test. A client reply plus the matching record is stronger evidence than an “installed” or “connected” label.
Before using the agent in a real project, create a scratch folder with a harmless README and ask it to read and summarize that file. Check the proposed tool action before allowing it. Model text output alone does not establish tool-calling support.
Troubleshooting
| Symptom | What to check |
|---|---|
| 401 / 403 | Check the full key, its enabled/expiry/IP settings, and group permission. Re-paste privately; do not publish the key. |
| 404 / model not found | Match the API format, base URL and exact model ID. Do not add /v1 twice or enter a full request path into a base-URL field. |
| 429 / credit or quota error | Check account credit, key quota and rate/concurrency limits. Repeated retries do not add balance or remove a limit. |
| Timeout / incomplete reply | Check the network and channel status. Keep the time and request ID for support; do not treat a partially received reply as a successful test. |
| Still uses the previous provider | Reopen the client, start a new conversation, and check its selected provider and any environment/config overrides. Restore a backup instead of deleting the whole configuration. |
| Settings moved or did not apply | Use hermes config path and hermes config check. Use the actual HERMES_HOME data directory rather than guessing a platform path. |
If you need help, send the app version, operating system, model ID, timestamp and request ID to Space Router support. Redact keys and private project content.
Backup, update and recovery
Before editing an existing setup, copy the file printed by hermes config path to a private backup. Keep the original provider name and model selection so you can return to them. Do not put credential backups in a project repository.
To recover, close the client, restore the specific file or select the previous provider, then reopen it. Keep conversations and other unrelated settings. Revoke an exposed key in Space Router and create a replacement only if it was actually exposed.
Use the application’s normal update flow. Recheck the provider selection and one real response after an update; do not rerun several installers together when one is still active.