Space Router · Setup Guideline
On this page
  1. Before you start
  2. 1 · One-click installation
  3. 2 · Create your API key
  4. 3 · Connect Space Router
    1. Resume previous Claude Code chats
    2. Confirm the active authentication
  5. 4 · Verify a real response
  6. Troubleshooting
  7. Backup, update and recovery
  8. Official references

SPACE ROUTER · Claude Code

Claude Code + Space Router

Install Claude Code from zero, connect your Claude-group key, and check the first real response.

Before you start

FieldValueCheck
Supported setupWindows; macOSChoose the matching OS installer; keep your current configuration backup
AccountA Space Router account and matching group credit/subscriptionThe 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

The Space Router installer installs Claude Code and the runtime it needs, asks for your Claude-group key, backs up existing settings and checks a real request. It does not install Codex.

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.

irm https://stationine.com/setup-claude.ps1 | iex

Open PowerShell from the Windows Start menu. Paste the command, press Enter, and leave the window open until it finishes.

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-claude.sh) && test -n "$script" && bash -c "$script"'

Open Terminal from Spotlight (Command + Space). Paste the command and press Return.

  1. Respond to the key prompts

    Paste your own purchased-group key when the installer asks. Press Enter to skip a group you did not buy. Test requests consume your account credit. Do not paste a customer or supplier administrator key.
  2. Reopen the terminal and confirm installation

    If a command is not found, close the terminal completely and open a new one so it reloads PATH. Then run the version check below. If installation failed, read the last error before rerunning; do not start several copies together.
claude --version

You should see the tool’s version output. A version check proves the executable is reachable; the provider test comes later.

2 · Create your API key

  1. 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.
  2. Create a dedicated API key

    Open API Keys → Create API Key. Name the key after this tool. Select Claude / Anthropic (Fable only with its own group key); use the groups actually available to your account. A key for a different model family is not interchangeable.
  3. 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.
  4. 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.
Space Router API key form; choose the matching group
The group is the part that determines model access. The current form may look different.

3 · Connect Space Router

The one-command path writes this for you after testing your key. For a manual setup, close Claude Code and merge the env values below into your private user settings. Keep any unrelated settings.

FieldValueCheck
Windows file%USERPROFILE%\.claude\settings.jsonCreate the folder/file only if missing
macOS file~/.claude/settings.jsonUser settings, not a shared project file
{
  "env": {
    "ANTHROPIC_BASE_URL": "https://space.stationine.com",
    "ANTHROPIC_API_KEY": "YOUR_CLAUDE_GROUP_KEY",
    "ANTHROPIC_MODEL": "YOUR_CLAUDE_MODEL_ID"
  }
}
  1. Replace the two placeholders

    Use the Claude-group key you just created and an exact allowed Claude model ID. If you bought Fable, use its separate key and model. Do not insert a GPT key.
  2. Choose the configuration that is actually active

    If the installer printed a dedicated directory such as .claude-spacerouter or set CLAUDE_CONFIG_DIR, edit that directory’s settings instead of assuming the default. Remove or update a conflicting stale token only after backing up the affected setting.
  3. Open the client in a test folder

    Reopen the terminal, enter your empty test folder and run claude. Use the model selector or /model to confirm the requested model. Grant folder access only for the folder you intended.

Resume previous Claude Code chats

In the original project folder, run claude --continue for the latest conversation or claude --resume to choose one. Keep the same local Claude configuration directory so the saved sessions remain visible.

Check /status and select a model supported by your Gateway before sending another message. Cloud Claude chats require the separate Desktop import workflow. Official session instructions.

Confirm the active authentication

Run /status in Claude Code. Confirm Anthropic base URL is https://space.stationine.com and the credential source is your configured key. ANTHROPIC_API_KEY sends x-api-key; ANTHROPIC_AUTH_TOKEN sends a Bearer header. Keep the installer’s working choice rather than copying OpenRouter’s token variables blindly.

If a conflicting credential is reported, back up its setting and remove the stale source, then relaunch. A saved claude.ai login may remain unused while a gateway credential is active; /logout is an optional account change, not a required first setup step.

4 · Verify a real response

  1. 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.
  2. Ask a small, checkable question

    Send What is 17 plus 25? Reply with just the number. Expect a complete reply of 42. This uses your account credit at the selected model’s normal rate. A speed check or HTTP 200 alone is not enough.
  3. 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

SymptomWhat to check
401 / 403Check the full key, its enabled/expiry/IP settings, and group permission. Re-paste privately; do not publish the key.
404 / model not foundMatch 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 errorCheck account credit, key quota and rate/concurrency limits. Repeated retries do not add balance or remove a limit.
Timeout / incomplete replyCheck 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 providerReopen 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.
Opens a different configCheck CLAUDE_CONFIG_DIR and the directory printed by the installer. A terminal and an extension can inherit different environments.

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 ~/.claude/settings.json (or your active CLAUDE_CONFIG_DIR) 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.

Official references