> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openmote.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.

# Cost Analytics

> Review Roomote inference spend by task type, environment, provider, model, or user.

Cost Analytics helps deployment teams understand how Roomote uses inference
across tasks, Fast-mode conversations, and automations. It reports the cost of
recorded model usage in US dollars, so you can spot the environments, models,
and work types that drive spend.

Any signed-in deployment user can open **Analytics** from the dashboard, then
select **Costs**.

## What you can review

The Costs view includes summary cards, a chart, and a detailed breakdown of
recorded inference usage. Use it to answer questions such as:

* which task types account for the most spend
* how much non-task inference, including Fast mode, contributes to spend
* whether a particular environment or model is driving costs
* how usage differs between people and automations
* how a provider's cost changes over time

The view starts grouped by **Task Type**. You can instead group or filter the
data by user, environment, provider, or model. Choose a time range before
comparing periods so the chart and breakdown use the same window.
Fast-mode inference that runs outside a launched task appears as **Non-task
inference** in the task-type breakdown.

## Exporting data

Select **Download data** to export the currently filtered detail rows as a CSV
file. Apply the time range and filters first so the export contains the slice
you intend to share or analyze elsewhere.

## Reading the results

Cost Analytics records inference usage reported by the configured model
providers. It is separate from [Anonymous Analytics](/anonymous-analytics):
cost data stays inside your deployment for your team to review, while anonymous
analytics is optional product telemetry sent to the Roomote team.

If a provider does not report pricing or usage for a request, that request
cannot contribute a cost to the view. Use provider and model filters to narrow
an investigation when totals do not match an external provider invoice.