Claude Code

Claude Code uses the Anthropic Messages protocol. To connect it to Moxus AI, do not use the OpenAI-compatible Base URL. Use https://moxus.cloud as the Anthropic Base URL and choose a model that supports Claude / Anthropic-compatible requests.

Values

Field	Value
API Key	`sk-your-key`
Anthropic Base URL	`https://moxus.cloud`
Final request URL	`https://moxus.cloud/v1/messages`
Model	A Claude or Anthropic-compatible model from Models and pricing

Install Claude Code

Install first, then run the version check separately. Do not copy the install command and the verification command as one block. After installation, you may need to reopen the terminal before claude is available.

macOS / Linux / WSL
Windows PowerShell
Windows CMD
npm

Install:

curl -fsSL https://claude.ai/install.sh | bash

Verify:

claude --version

Install:

irm https://claude.ai/install.ps1 | iex

If running claude afterward says PowerShell blocked claude.ps1, use claude.cmd directly instead of the .ps1 wrapper.Verify:

claude.cmd --version

Download the installer:

curl -fsSL https://claude.ai/install.cmd -o install.cmd

Run it:

install.cmd

Remove the installer:

del install.cmd

Verify:

claude --version

Install:

npm install -g @anthropic-ai/claude-code

Verify:

claude --version

Recommended: import configuration from an API key

On the Moxus AI API keys page, each key row has an Import configuration action. Choose Claude Code to generate a terminal script for the selected key and current site address.

Open the API keys page

Go to the Moxus AI console API keys page and find the key you want Claude Code to use.

Open Import configuration

Open the actions menu for that key, choose Import configuration, then switch to Claude Code.

Copy the script for your system

Use “macOS / Linux terminal” for macOS, Linux, or WSL. Use “Windows PowerShell” for Windows.

Run the script directly in your terminal

Open your terminal, paste the copied script directly into the same terminal window, and press Enter. The script works in both zsh and Bash, and the current terminal can use the new configuration as soon as it finishes.

The generated script does the following:

System	What it writes
macOS / Linux / WSL	Creates `~/.claude/moxus-code-env.sh`, writes `ANTHROPIC_API_KEY`, `ANTHROPIC_AUTH_TOKEN`, and `ANTHROPIC_BASE_URL`, then adds an auto-load block to `~/.zshrc` and `~/.bashrc`
Windows PowerShell	Sets user environment variables `ANTHROPIC_API_KEY`, `ANTHROPIC_AUTH_TOKEN`, and `ANTHROPIC_BASE_URL`, and also sets them for the current PowerShell window

Use the “macOS / Linux terminal” script for macOS, Linux, or WSL, and the PowerShell script for Windows. Both can be pasted and run directly in their respective terminals; no temporary file or extra command is required.

The script stores your API key in a local environment file or user environment variable. Do not share terminal screenshots, shell profiles, or environment files that contain the key.

Manual setup: current terminal only

Use a temporary environment variable if you do not want to use Import configuration yet. The commands apply only to the current terminal window and skip the user-level ~/.claude/settings.json, so an old setting cannot override the key you provide.

macOS / Linux / WSL
Windows PowerShell

ANTHROPIC_API_KEY="sk-your-key" \
ANTHROPIC_AUTH_TOKEN="sk-your-key" \
ANTHROPIC_BASE_URL="https://moxus.cloud" \
claude --setting-sources project,local

$env:ANTHROPIC_API_KEY="sk-your-key"
$env:ANTHROPIC_AUTH_TOKEN="sk-your-key"
$env:ANTHROPIC_BASE_URL="https://moxus.cloud"
claude.cmd --setting-sources "project,local"

ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN both use the same Moxus AI key to support different Claude Code versions and Anthropic-compatible clients.

Final request method

After configuration, Claude Code still sends Anthropic Messages requests. Moxus AI replaces the endpoint and key:

Field	Value
Method	`POST`
URL	`https://moxus.cloud/v1/messages`
Auth header	`x-api-key: sk-your-key`
Protocol header	`anthropic-version: 2023-06-01`
Model field	Use an Anthropic-compatible model from Models and pricing

It does not call https://moxus.cloud/v1/chat/completions, and it does not use the OpenAI-compatible Authorization: Bearer ... auth style.

Manual test

Use the command for your terminal to test the key, model, and Anthropic-compatible endpoint:

macOS / Linux / WSL
Windows PowerShell

curl https://moxus.cloud/v1/messages \
  -H "x-api-key: sk-your-key" \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{
    "model": "claude-opus-4-6",
    "max_tokens": 512,
    "messages": [
      {"role": "user", "content": "Introduce Moxus AI in one sentence"}
    ]
  }'

$headers = @{
  "x-api-key" = "sk-your-key"
  "anthropic-version" = "2023-06-01"
}
$body = @{
  model = "claude-opus-4-6"
  max_tokens = 512
  messages = @(@{ role = "user"; content = "Introduce Moxus AI in one sentence" })
} | ConvertTo-Json -Depth 4 -Compress

Invoke-RestMethod -Method Post -Uri "https://moxus.cloud/v1/messages" -Headers $headers -ContentType "application/json" -Body $body

If the request succeeds but Claude Code fails, confirm that the terminal launching Claude Code can read the variables:

macOS / Linux / WSL
Windows PowerShell

echo "$ANTHROPIC_BASE_URL"
echo "$ANTHROPIC_API_KEY"

echo $env:ANTHROPIC_BASE_URL
echo $env:ANTHROPIC_API_KEY

Do not share the full output of the second command.

Troubleshooting

Can I use the OpenAI Base URL for Claude Code?

Usually no. Claude Code uses the Anthropic Messages protocol. Configure https://moxus.cloud, and the tool will request /v1/messages. https://moxus.cloud/v1 is usually for OpenAI-compatible clients.

Why does Import configuration set both ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN?

This supports different Claude Code versions and Anthropic-compatible clients. Both variables use the same Moxus AI API key.

How do I remove the Moxus AI configuration for Claude Code?

These commands remove the Moxus AI environment file, shell auto-load markers, and user environment variables created by Import configuration. They do not remove other Claude Code settings.macOS / Linux / WSL:

rm -f "$HOME/.claude/moxus-code-env.sh"

for profile in "$HOME/.zshrc" "$HOME/.bashrc"; do
  [ -f "$profile" ] || continue
  sed -i.bak '/# Moxus AI Claude Code start/,/# Moxus AI Claude Code end/d' "$profile"
done

unset ANTHROPIC_API_KEY ANTHROPIC_AUTH_TOKEN ANTHROPIC_BASE_URL

Windows PowerShell:

[Environment]::SetEnvironmentVariable("ANTHROPIC_API_KEY", $null, "User")
[Environment]::SetEnvironmentVariable("ANTHROPIC_AUTH_TOKEN", $null, "User")
[Environment]::SetEnvironmentVariable("ANTHROPIC_BASE_URL", $null, "User")

Remove-Item Env:ANTHROPIC_API_KEY -ErrorAction SilentlyContinue
Remove-Item Env:ANTHROPIC_AUTH_TOKEN -ErrorAction SilentlyContinue
Remove-Item Env:ANTHROPIC_BASE_URL -ErrorAction SilentlyContinue

Close and reopen the terminal afterwards. If you manually added these values to ~/.claude/settings.json, remove only the matching env entries and keep the rest of the settings file.

Claude still requests Anthropic directly

Close and reopen the terminal, then confirm ANTHROPIC_BASE_URL is https://moxus.cloud. If you launch the client from a GUI, it may not read shell profiles. Start it from the terminal or use the client’s own settings surface.

How can terminal variables take priority over settings.json?

The env block in ~/.claude/settings.json can override terminal variables with the same names. Choose the option that fits your use case:

Prioritize this terminal only: Skip user settings at startup while continuing to load project and local settings: macOS / Linux / WSL:
ANTHROPIC_API_KEY="sk-your-key" ANTHROPIC_AUTH_TOKEN="sk-your-key" ANTHROPIC_BASE_URL="https://moxus.cloud" claude --setting-sources project,local
Windows PowerShell:
$env:ANTHROPIC_API_KEY="sk-your-key" $env:ANTHROPIC_AUTH_TOKEN="sk-your-key" $env:ANTHROPIC_BASE_URL="https://moxus.cloud" claude.cmd --setting-sources "project,local"
This does not load ~/.claude/settings.json, so an old endpoint or empty value there cannot override the terminal. User-level preferences in that file, such as theme and model preferences, are not loaded either.
Use Moxus AI persistently: Use Import configuration from the API keys page. If ~/.claude/settings.json still contains old values, remove or update only the conflicting ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, and ANTHROPIC_BASE_URL entries. Keep all unrelated personal settings and run claude normally afterward.

Claude Code does not provide a switch that makes Shell variables automatically outrank every settings file. --settings can override settings for one launch, but do not place an API key in that argument.

Windows PowerShell says running claude.ps1 is disabled

This is PowerShell execution policy blocking claude.ps1, not a broken Claude installation. The simplest fix is to use:

claude.cmd --version

or:

claude.cmd --setting-sources "project,local"

If you still want to run claude directly in the current window, temporarily allow script execution first:

Set-ExecutionPolicy -Scope Process Bypass

Why does project,local fail in Windows PowerShell?

In PowerShell, project,local must be quoted as one string. Use:

claude.cmd --setting-sources "project,local"

If your current directory is your home directory and you only want to skip ~/.claude/settings.json for a temporary session, use:

claude.cmd --setting-sources "local"

Which model name should I use?

Use the exact model name shown in Models and pricing. If the model does not support Anthropic Messages, use an OpenAI-compatible client or choose another model.

Overview

Platform

Guides

Integrations

Values

Install Claude Code

Recommended: import configuration from an API key

Manual setup: current terminal only

Final request method

Manual test

Troubleshooting

Next steps

​Values

​Install Claude Code

​Recommended: import configuration from an API key

​Manual setup: current terminal only

​Final request method

​Manual test

​Troubleshooting

​Next steps

Values

Install Claude Code

Recommended: import configuration from an API key

Manual setup: current terminal only

Final request method

Manual test

Troubleshooting

Next steps