Space Router · Setup Guideline
On this page
  1. Before you start
  2. 1 · Install from zero
  3. 2 · Create your API key
  4. 3 · Connect Space Router
    1. Choose the supported fallback
  5. 4 · Verify a real response
  6. Troubleshooting
  7. Backup, update and recovery
  8. Official references

SPACE ROUTER · Cursor

Cursor + Space Router

Install Cursor and connect a supported custom provider, or use an API-compatible extension inside the editor.

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 · Install from zero

Windows

  1. Download Cursor for Windows

    Open Cursor downloads, choose the Windows build matching your computer, then save and run the installer. Complete the normal installation and open Cursor.
  2. Open a test folder

    Create an empty folder such as SpaceRouter-Test and use File → Open Folder. Complete Cursor’s own sign-in if prompted; that account is not your Space Router API key.

macOS

  1. Download the matching Mac app

    Choose Apple Silicon or Intel on the official download page according to About This Mac. Open the downloaded disk image and move Cursor to Applications.
  2. Launch Cursor

    Launch it from Applications, complete the normal macOS/open-account prompts, then open an empty test folder.

Cursor’s own subscription features and third-party-provider features have separate availability rules. Use only a custom endpoint that your installed version actually exposes.

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

OpenRouter’s example uses its own /api/v1/cursor translation endpoint. Space Router has not been verified to expose that adapter; do not append /cursor to our URL or assume every Cursor Agent feature works.

  1. Open the model settings

    Open Cursor Settings → Models. Choose the provider for your purchased group and inspect whether this version exposes an override/custom base URL. The ordinary “API Key” field alone does not route traffic to Space Router.
  2. Configure only an exposed custom endpoint

    If an OpenAI-compatible override is present, use https://space.stationine.com/v1, your GPT-group key and an exact supported model ID. Save/enable the provider and select that model in a new chat. If an Anthropic override is present, use the root https://space.stationine.com with a Claude key.
  3. If the override is missing, use the extension route

    Open Extensions in Cursor and install Cline from its official publisher. Cline’s own documentation supports Cursor. Open its panel → Settings → OpenAI Compatible. Set the base URL, key and model as in the extension guide. This configures Cline inside Cursor, not Cursor’s built-in Agent.
  4. Verify the actual route

    Send the test in the specific panel you configured and check the matching Space Router usage row. Do not assume that enabling BYOK replaces every Cursor subscription feature or guarantees custom reasoning-model support.

Choose the supported fallback

If the native override cannot complete a response, use the Cline-in-Cursor steps above and select its OpenAI-compatible Space Router provider. Test in Cline’s panel. Cursor Tab, cloud agents and Cursor account billing are separate from that extension route.

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.
No custom base URL fieldUse the Cline extension route in this guide. A provider API key field alone is not a custom routing feature.

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 your named provider settings and the extension’s own configuration 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