Skip to main content

​
Anthropic (Claude)

Anthropic builds the Claude model family and provides access via an API. In Clawdia you can authenticate with an API key or reuse Claude Code CLI credentials (setup-token or OAuth).

​
Option A: Anthropic API key

Best for: standard API access and usage-based billing. Create your API key in the Anthropic Console.

​
CLI setup

clawdia onboard
# choose: Anthropic API key

# or non-interactive
clawdia onboard --anthropic-api-key "$ANTHROPIC_API_KEY"

​
Config snippet

{
  env: { ANTHROPIC_API_KEY: "sk-ant-..." },
  agents: { defaults: { model: { primary: "anthropic/claude-opus-4-5" } } }
}

​
Prompt caching (Anthropic API)

Clawdia does not override Anthropic’s default cache TTL unless you set it. This is API-only; Claude Code CLI OAuth ignores TTL settings. To set the TTL per model, use cacheControlTtl in the model params: 
{
  agents: {
    defaults: {
      models: {
        "anthropic/claude-opus-4-5": {
          params: { cacheControlTtl: "5m" } // or "1h"
        }
      }
    }
  }
}
Clawdia includes the extended-cache-ttl-2025-04-11 beta flag for Anthropic API requests; keep it if you override provider headers (see /gateway/configuration).

​
Option B: Claude Code CLI (setup-token or OAuth)

Best for: using your Claude subscription or existing Claude Code CLI login.

​
Where to get a setup-token

Setup-tokens are created by the Claude Code CLI, not the Anthropic Console. You can run this on any machine: 
claude setup-token
Paste the token into Clawdia (wizard: Anthropic token (paste setup-token)), or run it on the gateway host: 
clawdia models auth setup-token --provider anthropic
If you generated the token on a different machine, paste it: 
clawdia models auth paste-token --provider anthropic

​
CLI setup

# Reuse Claude Code CLI OAuth credentials if already logged in
clawdia onboard --auth-choice claude-cli

​
Config snippet

{
  agents: { defaults: { model: { primary: "anthropic/claude-opus-4-5" } } }
}

​
Notes

  • Generate the setup-token with claude setup-token and paste it, or run clawdia models auth setup-token on the gateway host.
  • If you see “OAuth token refresh failed …” on a Claude subscription, re-auth with a setup-token or resync Claude Code CLI OAuth on the gateway host. See /gateway/troubleshooting#oauth-token-refresh-failed-anthropic-claude-subscription.
  • Clawdia writes auth.profiles["anthropic:claude-cli"].mode as "oauth" so the profile accepts both OAuth and setup-token credentials. Older configs using "token" are auto-migrated on load.
  • Auth details + reuse rules are in /concepts/oauth.

​
Troubleshooting

401 errors / token suddenly invalid
  • Claude subscription auth can expire or be revoked. Re-run claude setup-token and paste it into the gateway host.
  • If the Claude CLI login lives on a different machine, use clawdia models auth paste-token --provider anthropic on the gateway host.
No API key found for provider “anthropic”
  • Auth is per agent. New agents don’t inherit the main agent’s keys.
  • Re-run onboarding for that agent, or paste a setup-token / API key on the gateway host, then verify with clawdia models status.
No credentials found for profile anthropic:default or anthropic:claude-cli
  • Run clawdia models status to see which auth profile is active.
  • Re-run onboarding, or paste a setup-token / API key for that profile.
No available auth profile (all in cooldown/unavailable)
  • Check clawdia models status --json for auth.unusableProfiles.
  • Add another Anthropic profile or wait for cooldown.
More: /gateway/troubleshooting and /help/faq.