Connect VS Code to Routescope (Cline Example)
Install Cline in VS Code and connect it to Routescope through OpenAI Compatible settings.
VS Code is a code editor. It does not call AI models by itself. The extension inside VS Code does the actual work. This guide uses the Cline extension and connects it to Routescope.
Everything is done by clicking and filling in forms. No coding is required.
Last updated: 2026-07-13
What You Need to Do
- Get a Routescope secret that starts with
sk-. - Install the Cline extension in VS Code.
- Enter the secret in Cline and choose a model.
Before You Start: Prepare Two Things
Keep these values nearby before configuring Cline.
1. Routescope Secret (API Key)
This secret is the passcode Cline uses to call models through Routescope.
- Open a browser and sign in to the Routescope console.
- In the left menu, open Token Management.
- Click Add Token.
- Use any token name, such as
Cline. - For first-time setup, keep quota, allowed models, and expiration at their defaults.
- Click Save.
- Back in the token list, click Copy Access Code on that token.
You will copy a string that starts with sk-, for example:
sk-xxxxxxxxxxxxxxxxSave the whole string, including the sk- prefix. Do not remove any characters.
Protect your secret
This secret is like a password. Do not send it to others or include it in screenshots or public documents.
2. An Available Model Name (Model ID)
The model ID is the AI model you want to use, such as gpt-5.4. It must be a model that is actually enabled for your account.
- Open Routescope Model Plaza.
- Find a model that your token can use.
- Copy the full Model ID. Copy the ID, not the display name.
Step 1: Install the Cline Extension
- Open VS Code.
- Click the Extensions icon in the left activity bar, the icon that looks like four squares. You can also press
Ctrl + Shift + X(Cmd + Shift + Xon macOS). - Type
Clinein the search box. - Find Cline in the results and click Install.
- After installation, a Cline icon appears in the left sidebar. Click it to open the Cline panel.
Step 2: Choose "Use Your Own API Key"
The first time you open Cline, it asks how you want to sign in.
- Click the gray Use your own API key button.
- Click Continue.
Step 3: Fill in These Four Fields in Order
After entering settings, fill in the following fields in order:
| Order | Field | Value | Plain explanation |
|---|---|---|---|
| 1 | API Provider | Select OpenAI Compatible | Some UIs may say "OpenAI-compatible"; it means the same thing |
| 2 | Base URL | https://api.routescope.ai/v1 | Routescope endpoint; it must end with /v1 |
| 3 | API Key | Your sk-... secret | Paste the full secret from preparation |
| 4 | Model ID | For example gpt-5.4 | This is a text input. Type a model enabled for your account |
If the UI has Verify, Test, or Save buttons, verify first and then save.
Base URL must include /v1
The easiest mistake is the Base URL. Use https://api.routescope.ai/v1. https://api.routescope.ai will not work here.
Step 4: Confirm It Is Really Connected
Asking the AI to say "configuration succeeded" is not enough. It may only repeat your words. Confirm it this way:
-
In Cline, send a normal message, for example:
First print "Routescope configuration succeeded", then list the top-level directory of the current project. -
After receiving a response, return to the Routescope console.
-
Open Operation Records or Call Records.
-
Check whether a new record appears from the same time, whether the status is successful, and whether billing looks normal.
Cline is truly connected only when Cline replies normally and Routescope shows the corresponding successful record.
If You Are Not Using Cline
Roo Code, Continue, and similar extensions follow the same idea as long as they support OpenAI-compatible providers and custom endpoints. The core fields are:
- Provider: OpenAI Compatible.
- Base URL:
https://api.routescope.ai/v1. - API Key: full
sk-.... - Model: a model ID enabled for your account.
If an extension does not have an OpenAI Compatible option, it likely does not support custom endpoints. Use Cline instead.
Troubleshooting
401 or 403
Check in this order: the secret is complete, the sk- prefix is present, the current model is allowed by the token, the token is not disabled or expired, quota remains, and IP restrictions are not blocking the request.
Which Base URL Should I Use?
Use https://api.routescope.ai/v1, including /v1.
Still Stuck
Send support a screenshot of the step where you are stuck, with the secret masked.
References
Last updated on