Get an API key
Create an API key in the xAI Console and enable billing for the account or team that should pay for Roomote usage.Configuration
Add xAI in Settings > Models and paste the key, or configure:xai/ prefix. Connecting xAI seeds
Grok 4.6 as the default coding model, and Grok chat models released after
the connection appear automatically, without a Roomote update. Models you
disable or remove stay that way. Deployments configured only through the
XAI_API_KEY environment variable start picking up new models once model
settings are first saved in Settings > Models. If both xAI API and a Grok
subscription are connected, Roomote prefers the subscription for xai/
models.
Cost behavior
API-key requests are billed by xAI according to model usage. Roomote records tokens and estimates cost from model metadata; the xAI Console and API pricing are authoritative. When a subscription is also connected, requests may consume the subscription allowance instead of API credits because it takes precedence.Verify setup
- save
XAI_API_KEY - confirm xAI models appear in Settings > Models
- pick a Grok chat model and assign it to a role
- run a small task and confirm usage in the xAI Console
Common issues
- The API key is not used. Disconnect the Grok subscription if you want
xai/requests to use separately billed API capacity. - Authentication or credit errors occur. Check key status, team selection, billing, and spend limits in the xAI Console.
- A model is unavailable. Refresh model metadata and confirm the API account can access the selected Grok model.