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

# OpenRouter

> Access models from many vendors through one OpenRouter account and key.

OpenRouter is a multi-provider inference gateway with a broad model catalog and
provider routing controls. It is Roomote's default inference option because one
connection can cover many recommended models.

## Get an API key

Create a key on the [OpenRouter keys page](https://openrouter.ai/settings/keys).
Add credits or configure the account's billing and set an optional key spending
limit before connecting it to Roomote.

## Configuration

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

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

Models use the `openrouter/<vendor>/<model>` form. Roomote adds its full curated
recommended set and offers balanced and quick-turnaround mapping presets. You
can still disable recommendations or add another OpenRouter model by slug.

## Cost behavior

OpenRouter deducts model and provider-route usage from the account balance. Its
model catalog shows current pricing and any route-specific differences. Roomote
records usage, estimates model cost, and displays the remaining key limit when
OpenRouter returns one. The [OpenRouter activity page](https://openrouter.ai/activity)
and account balance are authoritative.

## Verify setup

1. save `OPENROUTER_API_KEY`
2. confirm the recommended model list appears
3. apply a mapping preset or select a default coding model
4. run a small task and confirm the request appears in OpenRouter activity
5. check that Roomote shows a remaining key limit when the key has one

## Common issues

* **The key has no usable balance.** Add credits or raise its spending limit.
* **A model has no available route.** Check provider routing, privacy settings,
  and model availability in OpenRouter, or select a fallback model.
* **The credit line is absent.** Roomote only shows it when OpenRouter returns a
  numeric remaining limit; uncapped keys may not display one.