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. Check model selection before adding channels
  5. 4 · Verify a real response
  6. Troubleshooting
  7. Backup, update and recovery
  8. Official references

SPACE ROUTER · OpenClaw

OpenClaw + Space Router

Install OpenClaw, add a Space Router model provider, and verify it before adding channels or background services.

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

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-openclaw.ps1 | iex

Open PowerShell. The official installer can install its required runtime. The option below leaves onboarding for the next step:

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

Open Terminal and use the official installer. Finish installation before configuring the model provider.

Reopen the terminal, then check the CLI. On an existing installation, the upstream installer may refresh its own gateway service; review the official upgrade behavior before rerunning it.

openclaw --version
openclaw --help

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 GPT / OpenAI or Claude / Anthropic; 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

  1. Choose the initial configuration method

    Run openclaw onboard if you want its interactive setup. Choose a custom provider when offered. For the first model check, skip optional messaging channels and background-service installation; configure those separately after the API works.
  2. Back up and merge the provider

    The normal user config is ~/.openclaw/openclaw.json. Stop your own client before editing and back up the file. Merge the example into the existing object; keep other agents, channels and access settings.
{
  "models": {
    "mode": "merge",
    "providers": {
      "space-router": {
        "baseUrl": "https://space.stationine.com/v1",
        "apiKey": "YOUR_GPT_GROUP_KEY",
        "api": "openai-completions",
        "models": [
          {
            "id": "YOUR_GPT_MODEL_ID",
            "name": "Space Router GPT"
          }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "space-router/YOUR_GPT_MODEL_ID"
      }
    }
  }
}

Replace both occurrences of YOUR_GPT_MODEL_ID and the key placeholder. The provider ID before the slash must match the key under providers. mode: merge retains other providers. Do not invent context-window/token limits; use values confirmed for your selected model if your client requires them.

FieldValueCheck
GPT base URL / APIhttps://space.stationine.com/v1 · openai-completionsGPT-group key and model
Claude alternativehttps://space.stationine.com · anthropic-messagesReplace the key, model ID and agent model reference together

Save, run the configuration validation command supported by your installed version (see openclaw config --help), then reopen your own client. For a new local UI, openclaw dashboard opens the dashboard; send the first test there.

Check model selection before adding channels

Run openclaw models status and openclaw models list. If agents.defaults.models already defines an allowlist, add space-router/YOUR_GPT_MODEL_ID there too; setting primary alone does not expand an existing allowlist.

For a new local instance without a running gateway, use openclaw gateway run in a foreground terminal, then open openclaw dashboard in another terminal. If a gateway already runs, use it; do not launch a second copy or install a background service merely to test a model.

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.
Agent keeps its old modelMatch agents.defaults.model.primary to providerId/modelId, then validate and reload your own client.

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 ~/.openclaw/openclaw.json 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