> ## 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.

# Together AI

> Use Together AI's hosted open-model catalog for Roomote tasks.

Together AI hosts a broad catalog of open and specialized models behind one
inference API. Roomote's direct provider exposes a curated subset suited to
coding and agent work.

## Get an API key

Create a key from [Together AI API key settings](https://api.together.ai/settings/api-keys).
Make sure the account has credits or billing enabled for the models you select.

## Configuration

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

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

Roomote adds supported models with the `togetherai/` prefix. Enable the models
you want and assign the default coding and specialized roles. Provider model
names are case-sensitive, so use the IDs shown in Roomote rather than typing a
similar slug from another gateway.

## Cost behavior

Together AI charges the connected account according to the selected serverless
model or dedicated endpoint. Roomote records usage and estimates cost when model
metadata includes pricing; Together AI billing and the [pricing page](https://www.together.ai/pricing)
are authoritative.

## Verify setup

1. save `TOGETHER_API_KEY`
2. confirm Together AI models appear in **Settings > Models**
3. enable one model and assign it as the coding model
4. run a small task and confirm the request appears in Together AI usage

## Common issues

* **Authentication or balance errors occur.** Confirm the key is active and the
  account has enough credit.
* **A model ID is rejected.** Use the exact `togetherai/...` ID shown in Roomote;
  IDs from OpenRouter or another provider are not interchangeable.
* **Requests are queued or throttled.** Check the model's serverless limits or
  dedicated endpoint capacity and reduce concurrent Roomote tasks.