Client Tool Setup

RouteScope API client setup entry covering OpenAI API migration, Claude Code, Codex, Cursor, VS Code / Cline, cost-aware routing, and backup models.

These guides help you connect common clients and application requests to the RouteScope API. Create an API Key first, then fill in the Base URL, API Key, and model name for the guide you need.

Guide List

Switch from OpenAI API to RouteScope

Replace the Base URL, API Key, and model name in an OpenAI-compatible client.

How to Connect Claude Code to RouteScope

Point Claude Code to RouteScope through Anthropic-style environment variables.

How to Connect Codex to RouteScope

Configure Codex with config.toml, auth.json, and the OpenAI-compatible endpoint.

How to Connect Cursor to RouteScope

Connect Cursor to RouteScope through the Claude Code for VS Code extension.

How to Connect VS Code / Cline to RouteScope

Use Cline as an example for OpenAI-compatible VS Code extension setup.

How to Connect CC Switch to RouteScope

Manage and switch Claude Code, Codex, and other CLI provider configurations.

How to Connect OpenCode to RouteScope

Connect OpenCode Desktop to RouteScope through a custom OpenAI-compatible provider.

Route Simple Tasks to Qwen / DeepSeek to Reduce Costs

Choose Qwen or DeepSeek in your request or client for simple tasks.

Set Backup Models: Switch When OpenAI Fails

Retry with Claude, Qwen, or DeepSeek from your own application code.

OpenAI, Claude, Qwen, DeepSeek Pricing and Use Cases

Compare cost tendencies and verify real usage in operation records.