Install and configure CC-Switch for D1V PAI
Use one desktop app to manage provider credentials, generated CLI configuration, and the local routes required by Anthropic-protocol clients.
Before you start
Complete the Dashboard credential steps first. You need:
D1V_PAI_BASE_URL, normallyhttps://pai.d1v.ai/v1D1V_PAI_API_KEY, scoped to one project environment- A model ID returned by
GET /models
Use CC Switch 3.17.0 or newer for OpenAI Responses routing. Never choose a preset for another API provider: add a Custom provider so the endpoint remains D1V PAI.
Install the desktop app
Download the current release from CC-Switch Releases. On macOS:
brew tap farion1231/ccswitch
brew install --cask cc-switchInitialize each target CLI once before CC-Switch manages it: codex --help, claude --help, or the equivalent command for your client.
Add a custom provider
- Select the target application in the top app switcher.
- Click +, keep the application-specific provider tab, then select Custom.
- Name it
D1V PAIand paste the project key only into the API Key field. - Use the protocol values from the focused client guide. Codex can use Responses directly; Claude clients require local routing.
- Save and enable the provider, then restart the target application or terminal process.
The current add-provider screen. Choose Custom rather than another vendor preset. Source: official CC-Switch repository.
Protocol map
| Client | Endpoint entered | API format | Local route |
|---|---|---|---|
| Codex | https://pai.d1v.ai/v1 | OpenAI Responses | No |
| Claude Code | https://pai.d1v.ai | OpenAI Responses | Yes |
| Claude Desktop | https://pai.d1v.ai | OpenAI Responses | Yes |
| OpenAI-compatible client | https://pai.d1v.ai/v1 | OpenAI compatible | Usually no |
The Claude rows use the service root because CC-Switch builds and routes the upstream Responses request. Follow the client page instead of guessing where /v1 belongs.