Run Halon on your own AI account, or on Firefight's

You now decide which AI Halon runs on. See AI accounts.

Your own accounts. Admins add one or more accounts under AI accounts on the Workspace settings screen, from Anthropic, OpenAI, Google Gemini, OpenRouter, Amazon Bedrock, Google Vertex AI, Azure AI Foundry, DeepSeek, Mistral or xAI, and on a Firefight you run yourself Ollama and GPUStack too. Firefight checks each key with one short call when you save it. Halon tries the accounts from the top of the list, and an account that runs out of credit is skipped until a check passes again, with each admin told once in Slack.

Main and quick models. Each account has a main model for chats and investigations and a cheaper quick model for side jobs such as summaries, both filled in with the models Firefight recommends for that provider. See AI models.

A backup when a provider stops answering. Halon carries on from the same step with the account's backup model, then the next account, and says so in one line where its steps are shown.

Pick the model for a chat. The message box shows which model Halon answers with. Choose another your provider serves, each described in a few words, and the chat uses it from your next question. Each answer names the model that wrote it.

Or Firefight's AI. On Firefight's cloud, Halon can run on Firefight's own AI account instead, so you need no key. Admins buy Firefight credits from the Billing settings screen or during setup, and credits never expire.