Skip to main content
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 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:
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.

​
Model discovery and access

AWS exposes separate model catalogs for the two Bedrock endpoints. Mantle API keys can list the models on the regional Mantle /models endpoint. AWS documents native ListFoundationModels with AWS credentials and SigV4, not the Bedrock API key used by Roomote. Roomote therefore shows a curated Mantle list and preserves manually added amazon-bedrock/ model IDs instead of requesting broader AWS credentials. A model appearing in either regional catalog does not prove that the configured identity can invoke it. Invocation still depends on the region, IAM bedrock:InvokeModel permissions, AWS Marketplace requirements, and any model or account-specific access controls.

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

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