AI settings
AI settings are how the hive runs models: provider, key, tier, and usage. They sit under the platform plan, not beside it. There is no “AI plan” and no second invoice from InHive for tokens. InHive does not cap monthly tokens.
Only admins and managers can change them. Open the avatar menu → Organization settings → AI. Members see a reduced view — no keys, no optional limit.
InHive hosts speech-to-text for calls (Whisper). Every other model call — Ask, the assistant, digests, specs, suggestions, meeting actions, automations, knowledge embeddings — goes to your provider. InHive never spends a platform key on the hive’s work.
Before you start
Section titled “Before you start”| Plan | What you need |
|---|---|
| Studio | Your own provider key. Standard tier by default. |
| Team | Your own provider key. Frontier tier by default. |
| Enterprise | Your own provider key. Same product as Team. |
| Trial | Full Team for 14 days. Still paste a hive key before anyone relies on AI. |
If a feature is greyed out with an upgrade prompt, that is the platform plan, not a missing key. If Ask or the assistant says AI is not configured, that is a missing key.
Configure the hive
Section titled “Configure the hive”- Pick an API provider. OpenRouter is the usual choice — one key, many models. Direct vendors (OpenAI, Anthropic, xAI, Google, DeepSeek, Moonshot, Zhipu, Qwen, Mistral, Groq) need a key from that vendor’s console.
- Paste the API key and save. Required for every provider. The hive stores it encrypted. The browser never gets it back — only “a key is set.” Leave the field blank to keep the current key. Remove clears the key for the current provider only.
- Choose a model tier: Economy (fastest / cheapest), Standard (balanced), or Frontier (highest capability). The plan sets a default; changing the plan will follow that default unless you already picked a tier yourself.
- Optionally set models by capability — leave a row on “Tier default,” or pick a catalog model (or a custom
provider/model-id) for that kind of work. Groups cover digests, Ask, drafting, and the assistant. Open Per request type only if one capability needs a different model than its group. - Optionally set a monthly token limit if you want a hive spending stop. See Token spending below. Leave it empty for no hive cap.
- Test connection. A pass means the current key and model answered. A fail is the key, the provider, or the network — not the platform plan.
If you run Claude, Grok, Gemini, or another vendor without an embeddings API, also store an OpenRouter or OpenAI key. Knowledge ingest and search embeddings use that key. The completion provider stays the one you picked.
The embedding model itself is fixed. There is nothing to set for it — changing it would break search against existing knowledge.
Display name
Section titled “Display name”AI display name is optional. When set, people see it on Ask and the assistant. When empty, those surfaces are nameless — the label is just Ask. This is a label, not a second product.
Token spending
Section titled “Token spending”Token usage is the UTC calendar month. You pay your provider. InHive does not cap tokens. Managers can optionally set a monthly limit under Organization settings → AI. Empty means no hive cap. 0 pauses AI for the rest of the month.
Counted toward usage:
| Kind | What burns it |
|---|---|
| Completions | Ask, the assistant, digests, specs, Suggest with AI, meeting actions, automations, onboarding proposals |
| Embeddings | Knowledge ingest and search (files, notes, chat archives, transcripts) |
| MCP | Agent tools that call the same models — they share this usage. A looping agent will burn spend. |
Not counted: call speech-to-text (self-hosted Whisper). Pasted/imported meeting text still uses completions if you run AI actions.
If you set a limit, managers get an alert at 80%. When that limit is exhausted, AI calls stop until next month (or you raise it). There are no overage packs and no metered AI SKU from InHive.
Past-due billing keeps AI going for a short grace window, then pauses. See Billing.
Memory and corpus (Studio+)
Section titled “Memory and corpus (Studio+)”Two collapsed tiles on the same AI page:
- Memory health — useful Ask and assistant answers that cited a source, by week, person, and project. Askers tap useful / not useful under each answer; this is that score. An auto-judge mean sits beside it as a secondary number only.
- Corpus health — what is actually in project memory (files, notes, specs, transcripts, …), plus holes and skipped files or chat chatter. Re-index missing queues sources that never made it in.
If answers are thin, the usual fix is the knowledge base, not a different model.
Automations stay next door
Section titled “Automations stay next door”Scheduled workflows and their trust policy live under Organization settings → Automations, not here. See Automations.
Daily lines for each person live under Organization settings → Quotes. That screen is the switch, the day the weekly graph is rebuilt, the private note, and a rebuild for one person.