AI Proxy Node AI Proxy Node Docs

One-click Setup Scripts

Don't want to copy Base URL / environment variables by hand? Download the matching script, run it locally — it backs up your existing config and writes the new one in 3 steps.

⚠ Pick the right group when creating a Token

Each aiproxynode token is bound to exactly one group; cross-group calls are not auto-routed:

  • kiro group — runs Claude models (sonnet / opus / haiku)
  • gptpuls group — runs GPT models (gpt-5.5 / 5.4 / 5.3-codex)

If your client returns no available channels under group X, the token's group does not match the requested model.

Download

Pick your client scenario and download the script for your platform (.ps1 for Windows, .sh for macOS / Linux):

ScenarioRequired GroupWindows (.ps1)macOS (.sh)
VSCode + Claude CodekiroDownloadDownload
Claude Desktop + CLIkiroDownloadDownload
VSCode + Cline (using GPT)gptpulsDownloadDownload
Cursor + ClaudekiroDownloadDownload
Cursor mixed (choose at runtime)chosen at runtimeDownloadDownload

Prerequisites

  1. You've created a token in Console → Tokens (the group must match the script — see the "Required Group" column above)
  2. Your account has enough balance — insufficient balance returns 402 on the first call
  3. The matching client is installed (VSCode / Claude Desktop / Cursor, etc.)

Run on Windows (.ps1)

Method A · Right-click run (recommended)

  1. Download the matching .ps1 to any local folder (e.g. your Downloads folder)
  2. Right-click the file → Run with PowerShell
  3. Paste your token when prompted (input is hidden — that's normal)
  4. You're done when you see [4/4] complete; the terminal lists the next steps

Method B · Run manually in a terminal

PowerShell
# Go to the folder where you downloaded the script
cd $env:USERPROFILE\Downloads

# If your system blocks scripts the first time, allow them for this session
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

# Run (using VSCode + Claude Code as an example)
.\setup-vscode-claude.ps1
PowerShell version

Works with PowerShell 5.1 (built into Windows 10/11) and PowerShell 7+. The script auto-detects the version and uses compatible APIs.

Run on macOS / Linux (.sh)

bash
# Go to the download folder
cd ~/Downloads

# Add execute permission (optional — you can also run via bash directly)
chmod +x setup-vscode-claude.sh

# Run
bash setup-vscode-claude.sh

Same flow: enter the token when prompted (hidden input). Restart the relevant client when the script finishes.

What the script does

  1. Prompts for the token — input is hidden, processed in memory and zeroed after use, never written to logs
  2. Backs up the existing config — copies any file it will modify with a date suffix in the same folder (e.g. config.json.bak.20260516)
  3. Merges the new config — leaves your other settings alone; only changes the base URL / API key / model keys
  4. Tells you the next step — lists concrete actions like "restart VSCode" or "enable Claude Code in Settings"
About online connectivity verification

This version does NOT do an online check inside the script — once the config is written, it just prints "open your client and send a message to confirm". This is intentional, to avoid keeping the token in the script flow and reduce its exposure surface. If your first call fails, check in this order:

  • Whether the token's group matches the target model (kiro = Claude / gptpuls = GPT)
  • Whether you have enough balance (shown on the console home page)
  • Whether the client has been restarted to pick up the new config

Rollback / uninstall

Every modified config has a .bak.<date> backup right next to it — just rename it back to restore:

PowerShell
# Find the backups
ls $env:APPDATA\Code\User\settings.json.bak.*
# Restore (using 20260516 as an example)
mv settings.json.bak.20260516 settings.json
bash
# Same idea on macOS
ls ~/Library/Application\ Support/Code/User/settings.json.bak.*
mv settings.json.bak.20260516 settings.json

Troubleshooting

PowerShell says "cannot be loaded because running scripts is disabled on this system"

The system execution policy blocks scripts by default. Allow them for the current PowerShell session:

PowerShell
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

This only affects the current window and reverts when you close it; it does not change the system-wide policy.

macOS says "permission denied"

bash
chmod +x setup-xxx.sh && bash setup-xxx.sh

Client returns no available channels under group X

The token's group doesn't match the model you called. Go to Console → Tokens, edit the token to switch group, or create a new one. Note: calls right after switching may still see the old group (Redis cache on the backend, clears in a few minutes) — creating a fresh token to verify is faster.

Client returns 402 or insufficient_quota

Account balance or token quota is exhausted. Top up or raise the token quota in its settings.

Client returns 401 invalid api key

Token is wrong or has been deleted. Check the console, or create a new token and run the script again.

Don't want the script — configure manually

If you'd rather edit configs by hand, every manual setup is documented in API Reference → IDE Client Setup, including each client's environment variables, config file path, and JSON fields.

Script source

The scripts are plain text — open them in any browser to read (browsers won't execute them):

If you'd like to read before running, each script is under 200 lines and only invokes local commands (read token / back up / write JSON) — no outbound network requests.