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

# Moonshot AI (Kimi)

> Use Kimi models through the metered Moonshot AI Open Platform API.

Moonshot AI provides metered API access to Kimi models through its Open
Platform. This connection is separate from the membership-based [Kimi for
Coding](/providers/inference/kimi-for-coding) service.

## Get an API key

Create a key on the [Kimi API Platform keys page](https://platform.kimi.ai/console/api-keys).
Do not paste a Kimi for Coding membership key here; the two services use
different endpoints and billing.

## Configuration

Add **Moonshot AI (Kimi)** in **Settings > Models** and paste the Open Platform
key, or configure:

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

Models use the `moonshotai/` prefix. Roomote recommends available Kimi coding
models and can map a multimodal model to vision, planning, and review roles.

## Cost behavior

Open Platform requests draw from the account's API balance and are billed by
model usage. This is independent of any Kimi for Coding membership allowance.
Roomote records token usage and estimates cost from model metadata; the Kimi API
Platform balance and published pricing are authoritative.

## Verify setup

1. save `MOONSHOT_API_KEY`
2. confirm Moonshot AI models appear in **Settings > Models**
3. enable a `moonshotai/...` model and assign it to a role
4. run a small task and confirm usage appears in the Open Platform console

## Common issues

* **The key is rejected.** Confirm it was created at `platform.kimi.ai`, not in
  the Kimi Code membership console.
* **The balance does not change as expected.** Check that the selected model has
  the `moonshotai/` prefix rather than another gateway's Kimi model.
* **A model lacks a required capability.** Choose a Kimi model that supports the
  task's tool calling, context, or image-input requirements.