Connect tools: when to add /v1
Understand Base URL, key, model and protocol, then test the connection.
Three settings to fill
| Setting | Value |
|---|---|
| Base URL / API address | The running User Client's local endpoint, with protocol-specific path |
| API key / token | A local key created in User Client |
| Model | An available model ID from that key's catalog |
Use the address and key from the same Client. The website address, platform key and upstream provider key are different inputs.
Address examples
For root endpoint http://127.0.0.1:18000:
- OpenAI SDK Base URL normally uses
http://127.0.0.1:18000/v1; the SDK appends Chat Completions or Responses. - Claude Code's
ANTHROPIC_BASE_URLnormally uses the root and calls/v1/messages. - Raw HTTP uses a complete endpoint such as
http://127.0.0.1:18000/v1/responses.
Avoid duplicated /v1/v1. Do not supply a complete Responses endpoint as an SDK Base URL unless the tool explicitly asks for it. Copy your actual Client port.
View and copy the local endpoint at the top of the Local keys page.
Prefer generated configuration
View configuration helps you inspect/copy settings. Desktop Import local Agent previews files, makes backups and applies supported settings. CC Switch requires that application to be installed.
Choose the tool's OpenAI-compatible or Anthropic-compatible provider for its request format. Protocol conversion does not change the response format the tool expects to parse.
Minimal HTTP check
Replace both placeholders with your available model and local key:
curl http://127.0.0.1:18000/v1/responses \
-H "Authorization: Bearer YOUR_LOCAL_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"YOUR_AVAILABLE_MODEL","input":"Reply only OK","stream":false}'
PowerShell can use curl.exe; Bash line continuations are not portable to every Shell. Beginners can send the same short message directly from their configured tool.
Find the request in Usage records. Coding Agents also need a real tool-execution test. Continue with Codex, Claude Code or Other Agents.

