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

# Baseten

> Route Roomote tasks to supported foundation models through Baseten.

Baseten is a hosted inference platform for deploying and serving open and custom
models. Roomote's built-in provider exposes a curated set of Baseten-hosted
models through the standard Models workflow.

## Get an API key

Create a key from [Baseten API key settings](https://app.baseten.co/settings/api_keys).
Use a key from the workspace that has access to the models you plan to enable.

## Configuration

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

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

Roomote adds its recommended Baseten models after connection. Their IDs use the
`baseten/` prefix. Enable only models available to the key's workspace and set
the coding and specialized role mappings you want.

## Cost behavior

Baseten billing depends on the model endpoint and whether it uses serverless or
dedicated deployment capacity. Roomote records model usage and estimates costs
when catalog pricing is available, but the Baseten workspace bill is
authoritative. See [Baseten pricing](https://www.baseten.co/pricing/) for current
compute and inference terms.

## Verify setup

1. save `BASETEN_API_KEY`
2. confirm Baseten 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 Baseten observability

## Common issues

* **Authentication fails.** Confirm the key is active and belongs to the
  intended Baseten workspace.
* **A model cannot run.** Verify that the workspace can access that foundation
  model or deployment and refresh Roomote's model metadata.
* **Cold requests are slow.** Check the endpoint's autoscaling and minimum
  replica settings in Baseten; Roomote does not control model replicas.