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

# Amazon Bedrock

> Connect Roomote to native Amazon Bedrock and Bedrock Mantle models.

Amazon Bedrock provides managed access to models from multiple model developers
inside AWS. Roomote supports both native Bedrock Runtime models and models
served through Bedrock's Mantle endpoints. Both use a Bedrock API key, so setup
does not require long-lived IAM access-key and secret-key credentials.

## Get a Mantle API key

Open the [Bedrock API keys console](https://us-east-1.console.aws.amazon.com/bedrock-mantle/api-keys)
and generate a key. Select the AWS region where you intend to use Bedrock before
creating it; model availability and the key are region-dependent.

## Configuration

Add **Amazon Bedrock** in **Settings > Models**, enter the Mantle API key, and
optionally specify its AWS region. Environment-variable configuration uses:

```sh theme={null}
AWS_BEARER_TOKEN_BEDROCK=...
AWS_REGION=us-east-1
```

Roomote exposes Mantle models with the `bedrock-mantle/` prefix and OpenCode's
native Bedrock provider models with the `amazon-bedrock/` prefix. The region
defaults to `us-east-1` when omitted. Native Claude and other Bedrock Runtime
models can use regional and cross-region inference-profile prefixes, such as
`eu.`, `us.`, or `global.`. OpenAI models selected through the native provider
continue to use Mantle's Responses endpoint automatically. Enable only models
your account and configured region can access, then choose the default and role
mappings.

Roomote keeps Mantle models as the recommended defaults. Use native Bedrock
models when you need standard Bedrock Runtime behavior or a regional inference
profile that is not available through Mantle. Inference-profile ARNs are not
supported through Roomote's hosted inference gateway; use the plain model or
cross-region profile ID instead.

## Cost behavior

Bedrock bills the AWS account according to the selected model, request type,
region, and any provisioned capacity. Roomote records model usage and estimates
cost from model metadata; AWS billing remains authoritative. Review current
rates on the [Bedrock pricing page](https://aws.amazon.com/bedrock/pricing/).

## Verify setup

1. save the Mantle API key and matching region
2. confirm Amazon Bedrock models appear in **Settings > Models**
3. enable a Mantle or native model available in that region and assign it to a role
4. run a small task and confirm usage appears in the task and AWS account

## Common issues

* **The key is rejected.** Confirm it is a Bedrock Mantle API key, not an AWS
  access key, and that it was created in the configured region.
* **A model fails although it is listed.** Confirm the model is available to
  your AWS account in `AWS_REGION` and that any required model access is enabled.
* **A native Anthropic model is denied.** Complete Anthropic's first-time-use
  and AWS Marketplace access requirements for Bedrock Runtime. These
  requirements do not apply to the same model through Mantle.
* **Costs differ from Roomote's estimate.** AWS may apply regional, caching,
  provisioned-throughput, or model-specific pricing that changes independently.