How your AI is powered

Transcribing a meeting, reading it through an agent, searching by meaning: all of it is AI work, and AI work runs on somebody’s provider account. This page is where a workspace decides whose. Find it under Settings → AI Providers.

Choose how your AI is powered

Three modes, and the difference between them is what happens when a key isn’t there.

• Jinn credits — everything runs on Jinn’s own provider accounts. Nothing to set up, and nothing to keep alive.
• Only my own keys — each provider runs on a key you’ve added. A provider with no active key is unavailable, and Jinn refuses the call rather than quietly using something else. Choose this when it matters that your content only ever reaches accounts you control.
• My keys, with Jinn credits as backup — your keys go first, and Jinn credits cover any provider whose key is missing or switched off, so nothing stops working while you fix it.

Whichever mode you’re on, it decides whose account the AI work runs on and how much of it you get, not which parts of Jinn you can open — every workspace has the same meetings, agents, chat and docs. Your instance administrator can require own keys for the workspace, in which case the choice is made for you and Jinn says so instead of leaving a control that won’t move.

What each provider does

Each one has a job:

• Chat and reasoning, including the analysis agents produce
• Transcription — turning meeting audio into text
• Indexing — making your content findable by meaning
• Web search, for the parts of Jinn that read the internet
• Images, and applying AI-suggested edits

You don’t need every provider. You need the ones behind the features you use — and if you plan to record meetings, that includes whichever one transcribes.

Key states, and what to do about each

Jinn switches a key off for one of three reasons, and each says what to do:

• Your provider kept rejecting it. Check it again to bring it back, or replace it.
• Your account with them can’t serve calls. Usually a balance. Top it up, then check the key again.
• Jinn can’t read the key any more. Paste it again.

Owners and admins get a notification when this happens, so a dead key doesn’t go unnoticed until somebody complains. Check this key again re-tests it. Replace this key takes a new one. Delete this key removes it, and Jinn warns first that it can’t be shown again or brought back.

What stops loudly, and what stops quietly

This is the part worth remembering. Chat and transcription fail loudly. If the key they need is gone, they say so. You get an error, or a failed transcription with Try again on it. Nothing is lost silently. Indexing stops quietly. If the workspace runs on its own keys and the key behind indexing isn’t usable, indexing does nothing at all — no error, no retry, no notification. New recordings and write-ups never become findable by meaning. So when something has disappeared from search, check this page first. It’s the most common cause and the one that gives you no other clue.

What indexing does

Indexing reads your transcripts and write-ups and makes them findable by what they mean rather than by exact wording. It’s how a search for pricing finds the meeting where nobody said the word pricing. It runs by itself over new content, and there’s nothing to schedule.

Where to go next