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

# OpenAI

> Use OpenAI API models with separately billed API capacity.

The OpenAI provider gives Roomote direct, usage-billed API access to supported
OpenAI models. It is separate from [ChatGPT Subscription](/providers/inference/chatgpt),
which uses an eligible ChatGPT plan instead of API credits.

## Get an API key

Create a key on the [OpenAI API keys page](https://platform.openai.com/api-keys).
The key's project must have billing, model access, and suitable usage limits.

## Configuration

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

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

Roomote adds recommended models under the `openai/` prefix. Apply a recommended
mapping or choose separate models for coding, helper, planning, and review work.
When both OpenAI API and ChatGPT Subscription are connected, they expose the
same model prefix and Roomote uses the subscription. Disconnect ChatGPT
Subscription before using billed OpenAI API capacity.

## Cost behavior

OpenAI API requests are billed to the API project by model and token usage; a
ChatGPT Plus or Pro subscription does not include API credits. Roomote records
usage and estimates cost from model metadata. The [OpenAI API pricing page](https://openai.com/api/pricing/)
and project bill are authoritative.

## Verify setup

1. save `OPENAI_API_KEY`
2. confirm OpenAI models appear and enable at least one
3. assign an `openai/...` model to a role
4. run a small task and confirm usage appears in the OpenAI project

## Common issues

* **The key works elsewhere but not in Roomote.** Disconnect ChatGPT Subscription
  first, then confirm the API key is active and its project has API billing.
* **Quota or rate-limit errors occur.** Check project spend limits, usage tier,
  and model-specific limits in the OpenAI Platform.
* **The wrong connection is used.** If ChatGPT Subscription is also connected,
  disconnect the subscription before using billed OpenAI API capacity.