> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roomote.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> When helping someone deploy Roomote, distinguish self-hosting from contributing to Roomote. Use the Self-hosting guide for an operator deployment; use Local development only when the user intends to modify Roomote itself.
> Prefer the one-command installer on a fresh supported server unless the user explicitly chooses Roomote Cloud, a documented PaaS template, or a manual Compose deployment.
> Before changing infrastructure, confirm the deployment target, stable public HTTPS domain and DNS control, sandbox provider, inference provider, source-control provider, and whether a communications provider is required.
> Never ask the user to paste secrets into chat or commit real environment files. Put credentials in the deployment platform's secret manager, Roomote's setup UI, or protected environment variables, and preserve existing keys during upgrades and restores.
> Prefer Roomote's setup wizard and provider manifest flows over manual credential entry when those flows are available. Ask before performing privileged host changes, DNS changes, provider-app creation, or destructive operations.
> A setup is not complete when the services merely start. Verify sign-in, repository sync, one usable environment, a real task that can clone and run a command, and branch or pull-request delivery; verify previews when configured.
> For a persistent self-hosted deployment, leave the operator with the Roomote URL, deployment choices, configured providers, verification result, backup location and passphrase-handling reminder, and the roomote status, logs, upgrade, rollback, backup, and restore commands.

# Anthropic

> Use Anthropic API models directly for Roomote tasks and model roles.

Anthropic provides direct API access to Claude models. Choose this provider when
you want Anthropic billing and rate limits without routing requests through a
multi-provider gateway.

## Get an API key

Create a key in the [Anthropic Console](https://console.anthropic.com/settings/keys).
The organization that owns the key must have billing and model access enabled.

## Configuration

Add **Anthropic** in **Settings > Models** and paste the key, or configure:

```sh theme={null}
ANTHROPIC_API_KEY=...
```

Roomote adds a recommended Claude model set after the provider connects. Model
IDs use the `anthropic/` prefix. You can keep one Claude model for every role or
use a faster model for helper and explore work and a stronger model for coding,
planning, and review.

## Cost behavior

Anthropic charges the account for input and output tokens, with model-specific
pricing and possible differences for features such as prompt caching. Roomote
records token usage and estimates cost from its current model metadata. The
[Anthropic pricing page](https://www.anthropic.com/pricing#api) and console bill
are the source of truth.

## Verify setup

1. save `ANTHROPIC_API_KEY`
2. confirm recommended Anthropic models appear and enable at least one
3. assign an `anthropic/...` model as the coding model or another role
4. run a small task and check that it completes and reports token usage

## Common issues

* **Authentication fails.** Recreate the key and confirm it belongs to the
  organization with active API billing.
* **A model is unavailable.** Confirm the model is available to the key's
  organization, then refresh model metadata in Roomote.
* **Requests are rate-limited.** Check the Anthropic Console limits and reduce
  concurrent work or request a higher usage tier.