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

# Requesty

> Route Roomote model calls through Requesty's multi-provider AI gateway.

Requesty is a multi-provider inference gateway with centralized routing,
fallbacks, usage analytics, and cost controls. Use it when you want one
connection for models from several vendors.

## Get an API key

Sign up for Requesty and create a key on the [API Keys page](https://app.requesty.ai/api-keys).
Add credits or configure billing and any key-level spending limits before
connecting the key to Roomote.

## Configuration

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

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

Roomote exposes its recommended Requesty models under the `requesty/<model>`
prefix. Some model IDs include a region suffix such as `@eu`. Apply the
recommended mapping or select models individually for each role.

## Cost behavior

Requesty bills routed model usage according to the account's plan, provider
pricing, and any bring-your-own-key configuration. Roomote records token usage
and estimates model cost from metadata, but Requesty's usage dashboard and bill
are authoritative. See [Requesty pricing](https://www.requesty.ai/pricing) for
current terms.

## Verify setup

1. save `REQUESTY_API_KEY`
2. confirm Requesty models appear in **Settings > Models**
3. apply the recommended mapping or assign a model to the coding role
4. run a small task and confirm it appears in [Requesty analytics](https://app.requesty.ai/analytics)

## Common issues

* **The key is rejected.** Confirm it is active and belongs to the intended
  Requesty organization.
* **A model cannot be routed.** Check model availability, approved-model rules,
  routing policies, regional support, and account balance in Requesty.
* **A spending limit blocks tasks.** Raise the applicable Requesty key or
  organization limit, or choose a model with available budget.