Claude Code

Claude Code talks the Anthropic Messages format, so it works with InterOdin unchanged. Point it at the API origin, give it your key, and set every model slot to odin-v1. The block below also switches off the Anthropic-only extras that cause most gateway errors.

Quick startCopy Anchor Link

The setup script adds a separate claudeodin command: the same Claude Code, running on Odin models with your InterOdin key. Your normal claude is not touched and keeps using your Claude account, so you can use both side by side. This is the recommended way.

claudeodin keeps its settings, sessions and history in its own folder, ~/.claude-odin. The script writes the settings below there, puts the claudeodin launcher next to claude (or in ~/.local/bin, and tells you if that folder needs adding to your PATH), and asks for your key with the input hidden.

1. Create an API key in the console (it starts with io-sk-).
2. Download the setup script, then run it with Node 18 or newer:

curl -fsSL https://docs.interodin.com/claude-code-setup.mjs -o claude-code-setup.mjs
node claude-code-setup.mjs

3. Run claudeodin. No login screen appears, because the key is already set. On the first start Claude Code asks for a theme once, as it does for any new settings folder.

Prefer to make your normal claude use InterOdin instead, with no separate command? Run node claude-code-setup.mjs --replace-claude. It writes the same settings into ~/.claude/settings.json, keeping your other settings and backing up the old file first.

The script then checks the key for free (it lists the models the key may use; --no-check skips this) and warns about the usual conflicts: an ANTHROPIC_API_KEY in your shell or a signed-in Claude.ai account. To undo everything later, run node claude-code-setup.mjs delete (see Remove InterOdin and go back to normal). The script is short and has no dependencies, so you can read it before running it. Prefer to do it by hand? The next section shows the exact settings it writes, and Add claudeodin by hand shows the launcher.

Configure settings.jsonCopy Anchor Link

Add these to ~/.claude/settings.json, which applies to all your projects. Or put the env block in .claude/settings.local.json in one project (the modelPicker block only works in ~/.claude/settings.json).

{
  "env": {
    "ANTHROPIC_BASE_URL": "https://api.interodin.com",
    "ANTHROPIC_AUTH_TOKEN": "io-sk-your-key",
    "ANTHROPIC_MODEL": "odin-v1[1m]",
    "ANTHROPIC_DEFAULT_OPUS_MODEL": "odin-v1[1m]",
    "ANTHROPIC_DEFAULT_SONNET_MODEL": "odin-v1[1m]",
    "ANTHROPIC_DEFAULT_HAIKU_MODEL": "odin-flash",
    "CLAUDE_CODE_SUBAGENT_MODEL": "odin-v1[1m]",
    "CLAUDE_CODE_MAX_CONTEXT_TOKENS": "250000",
    "CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS": "1",
    "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1",
    "ENABLE_CLAUDEAI_MCP_SERVERS": "false"
  },
  "modelPicker": {
    "replaceBuiltInOptions": true,
    "options": [
      { "model": "odin-v1[1m]", "label": "Odin v1", "description": "Most capable, 1M context" },
      { "model": "odin-flash", "label": "Odin Flash", "description": "Fast and cheaper" }
    ]
  }
}

Then start claude as usual.

Don't commit a settings file that contains your key. For a shared project, keep the key in .claude/settings.local.json, which is git-ignored, or in your shell environment.

Or use environment variablesCopy Anchor Link

The same variables work from your shell profile:

export ANTHROPIC_BASE_URL="https://api.interodin.com"
export ANTHROPIC_AUTH_TOKEN="io-sk-your-key"
export ANTHROPIC_MODEL="odin-v1[1m]"
export ANTHROPIC_DEFAULT_OPUS_MODEL="odin-v1[1m]"
export ANTHROPIC_DEFAULT_SONNET_MODEL="odin-v1[1m]"
export ANTHROPIC_DEFAULT_HAIKU_MODEL="odin-flash"
export CLAUDE_CODE_SUBAGENT_MODEL="odin-v1[1m]"
export CLAUDE_CODE_MAX_CONTEXT_TOKENS="250000"
export CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS="1"
export CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC="1"
export ENABLE_CLAUDEAI_MCP_SERVERS="false"
unset ANTHROPIC_API_KEY

Add claudeodin by handCopy Anchor Link

The script's launcher only sets one variable, CLAUDE_CONFIG_DIR, so Claude Code reads its settings from ~/.claude-odin instead of ~/.claude. To build it yourself, put the settings.json above in ~/.claude-odin/settings.json, then create the launcher in a folder on your PATH:

macOS / Linux (~/.local/bin/claudeodin, then chmod +x ~/.local/bin/claudeodin):

#!/bin/sh
CLAUDE_CONFIG_DIR="$HOME/.claude-odin" exec claude "$@"

Windows (claudeodin.cmd, in the same folder as claude.cmd):

@echo off
setlocal
set "CLAUDE_CONFIG_DIR=%UserProfile%\.claude-odin"
set "ClaudeExe="
for %%E in (exe cmd) do if not defined ClaudeExe for %%I in (claude.%%E) do set "ClaudeExe=%%~$PATH:I"
"%ClaudeExe%" %*

It looks claude up in your PATH folders only. A plain claude %* would let Windows run a claude.cmd planted in the current folder (a cloned repository, for example) instead of the real one.

Or skip the file and add a shell alias: alias claudeodin='CLAUDE_CONFIG_DIR="$HOME/.claude-odin" claude' in ~/.bashrc or ~/.zshrc.

Remove InterOdin and go back to normalCopy Anchor Link

One command undoes the setup, whichever way you set it up:

node claude-code-setup.mjs delete

(remove, uninstall and --remove do the same.) It removes the claudeodin launcher and deletes exactly what the setup added to ~/.claude-odin/settings.json and ~/.claude/settings.json: the InterOdin variables and the Odin v1 / Odin Flash list in /model. Your other settings stay as they are, and each file is backed up first. A model list you set up yourself is left alone. The ~/.claude-odin folder itself stays, with the claudeodin sessions and history in it; delete it if you do not need them.

If you used claudeodin, your normal claude was never changed and there is nothing else to do. If you used --replace-claude, restart Claude Code and run /login to use your Claude account again. /model then shows Claude's own models.

Set it up by hand instead? Delete the same entries yourself:

• The claudeodin launcher or alias, and the ~/.claude-odin folder.
• In ~/.claude/settings.json (or .claude/settings.local.json): the env entries from the table above and the modelPicker block.
• In your shell profile: the export lines from Or use environment variables, then open a new terminal. In the current one, unset ANTHROPIC_BASE_URL ANTHROPIC_AUTH_TOKEN ANTHROPIC_MODEL ANTHROPIC_DEFAULT_OPUS_MODEL ANTHROPIC_DEFAULT_SONNET_MODEL ANTHROPIC_DEFAULT_HAIKU_MODEL CLAUDE_CODE_SUBAGENT_MODEL CLAUDE_CODE_MAX_CONTEXT_TOKENS clears them (PowerShell: Remove-Item Env:ANTHROPIC_BASE_URL and so on).

Your InterOdin key keeps working for other tools. Revoke it in the console if you no longer need it.

Check that it worksCopy Anchor Link

Inside Claude Code, run /status. It should show the base URL above. Then send a short prompt. The request appears within seconds in the console's request logs, against the key you used.

Good to knowCopy Anchor Link

• Prices in /model. The picker shows prices such as "$5/$25 per Mtok" from Claude Code's own table of Claude models. That label is display only: Claude Code has no setting to change it, and you are billed InterOdin's prices for odin-v1 and odin-flash (see the console's usage and request logs).
• Billing. One visible turn can be several API requests: tool calls, retries, compaction. Each request is billed for its own tokens. Watch usage per key in the console, and consider giving Claude Code its own key with a monthly spend limit.
• Caching is automatic and best-effort, so long sessions reuse their prompt prefix. No extra setup is needed. See Prompt caching.
• Thinking. Both models think by default. Thinking is on or off only: there are no effort levels or budgets, so those settings have no effect. See Extended thinking.
• Images. Odin v1 is text-only. Pasting a screenshot fails with 400 image_input_not_supported. If Claude Code reads an image file itself (for example one it just downloaded), the image is replaced by a short note and the session carries on. Run /clear or /rewind if a session you started elsewhere keeps failing on an image in its history.
• Documents. Attaching a PDF or another document fails with 400 unsupported_content. Paste the text instead.
• Web search. Claude Code's WebSearch tool works. Each search is billed on top of the tokens, at the per-search price on the pricing page on the InterOdin website. A request runs at most 5 searches.
• Client tools such as the shell, file edits and your own custom tools are ordinary function tools and work normally. Other server-side tools are removed from the request without an error.
• [1m] suffix. InterOdin accepts a model id such as odin-v1[1m] and ignores the suffix. Don't rely on it to set Claude Code's context window. Use CLAUDE_CODE_MAX_CONTEXT_TOKENS instead.

TroubleshootingCopy Anchor Link