Skip to main content

​
Provider authentication

Fased supports OAuth and API keys for model providers. For Anthropic accounts, we recommend using an API key. For Claude subscription access, use the long‑lived token created by claude setup-token.
This page covers model-provider authentication. Gateway and Control UI login are separate: use gateway.auth for the Gateway token/password/trusted-proxy mode, and see Gateway security for page and API protection.
For normal browser setup, open the selected Agent and use Agent > Models. That page owns provider sign-in, API-key entry, per-Agent model roles, and model selection. The CLI commands below are for automation, repair, or advanced operator workflows. See /concepts/oauth for the full OAuth flow and storage layout. For SecretRef-based auth (env/file/exec providers), see Secrets Management. If you’re using Anthropic directly, use an API key.
  1. Create an API key in the Anthropic Console.
  2. Put it on the gateway host (the machine running fased gateway).
export ANTHROPIC_API_KEY="..."
fased models status
  1. If the Gateway runs under systemd/launchd, prefer putting the key in ~/.fased/.env so the daemon can read it:
cat >> ~/.fased/.env <<'EOF'
ANTHROPIC_API_KEY=...
EOF
Then restart the daemon (or restart your Gateway process) and re-check: 
fased models status
fased doctor
If you’d rather not manage env vars yourself, the onboarding wizard can store API keys for daemon use: fased onboard. The Control UI can also store provider credentials from Agent > Models. See Help for details on env inheritance (env.shellEnv, ~/.fased/.env, systemd/launchd).

​
Anthropic: setup-token (subscription auth)

For Anthropic, the recommended path is an API key. If you’re using a Claude subscription, the setup-token flow is also supported. Generate the token in an interactive terminal: 
claude setup-token
Then paste it into Fased on the gateway host: 
fased models auth setup-token --provider anthropic
If the token was copied from another machine or automation flow, paste it manually: 
fased models auth paste-token --provider anthropic
If you see an Anthropic error like: 
This credential is only authorized for use with Claude Code and cannot be used for other API requests.
…use an Anthropic API key instead. Manual token entry (any provider; writes auth-profiles.json + updates config): 
fased models auth paste-token --provider anthropic
fased models auth paste-token --provider openrouter
Auth profile refs are also supported for static credentials:
  • api_key credentials can use keyRef: { source, provider, id }
  • token credentials can use tokenRef: { source, provider, id }
Automation-friendly check (exit 1 when expired/missing, 2 when expiring): 
fased models status --check
Optional ops scripts (systemd/Termux) are documented here: /automation/auth-monitoring
claude setup-token requires an interactive TTY.

​
Checking model auth status

fased models status
fased doctor

​
API key rotation behavior (gateway)

Some providers support retrying a request with alternative keys when an API call hits a provider rate limit.
  • Priority order:
    • FASED_LIVE_<PROVIDER>_KEY (single override)
    • <PROVIDER>_API_KEYS
    • <PROVIDER>_API_KEY
    • <PROVIDER>_API_KEY_*
  • Google providers also include GOOGLE_API_KEY as an additional fallback.
  • The same key list is deduplicated before use.
  • Fased retries with the next key only for rate-limit errors (for example 429, rate_limit, quota, resource exhausted).
  • Non-rate-limit errors are not retried with alternate keys.
  • If all keys fail, the final error from the last attempt is returned.

​
Controlling which credential is used

​
Per-session (chat command)

Use /model <alias-or-id>@<profileId> to pin a specific provider credential for the current session (example profile ids: anthropic:default, anthropic:work). Use /model (or /model list) for a compact picker; use /model status for the full view (candidates + next auth profile, plus provider endpoint details when configured).

​
Per-agent (CLI override)

Set an explicit auth profile order override for an agent (stored in that agent’s auth-profiles.json): 
fased models auth order get --provider anthropic
fased models auth order set --provider anthropic anthropic:default
fased models auth order clear --provider anthropic
Use --agent <id> to target a specific agent; omit it to use the configured default agent.

​
Troubleshooting

​
“No credentials found”

If the Anthropic token profile is missing, run claude setup-token on the gateway host, then re-check: 
fased models status

​
Token expiring/expired

Run fased models status to confirm which profile is expiring. If the profile is missing, rerun claude setup-token and paste the token again.

​
Requirements for setup-token

  • Claude Max or Pro subscription (for claude setup-token)
  • Claude Code CLI installed (claude command available)