> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jinn.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a key from an AI provider and add it to Jinn

> Which provider keys you need, where each provider hands them out, how to add and to keep them working in Jinn.

> [!NOTE]
>
> Only workspace owners and admins can add keys under **Settings** → **AI Providers**. You
> don't need to read this page if your workspace runs on **Jinn credits**.

If your workspace runs on its own keys, every key comes from the provider's own site: you
open an account there, the provider bills you for what Jinn uses, and you paste the key into
Jinn. This page tells you which keys you need and where to get each one.

Choosing between Jinn credits and your own keys is covered in
[How your AI is powered](https://docs.jinn.so/workspace/ai-and-indexing.md).

## Decide which keys you need

Jinn takes keys from three providers. Add the ones behind the features your team uses.

| Provider | What it does in Jinn | Where to get a key | How to get a key |
| - | - | - | - |
| **Gemini** (Google) | Chat, meeting transcription, and the indexing behind search | [Google guide](https://aistudio.google.com/apikey) | [Using Gemini API keys](https://ai.google.dev/gemini-api/docs/api-key) |
| **OpenAI** | Chat, content actions and image generation | [OpenAI Platform](https://platform.openai.com/api-keys) | [OpenAI guide](https://developers.openai.com/api/docs/quickstart) |
| **Exa** | Internet search and reading web pages | [Exa dashboard](https://dashboard.exa.ai/api-keys) | [Exa guide](https://exa.ai/docs/get-started/quickstart) |

Start with Gemini. It transcribes meeting audio and it does the [indexing](https://docs.jinn.so/find/search.md)
that makes meetings findable by meaning, and it can run [chat](https://docs.jinn.so/find/ask-a-question.md) and
[agents](https://docs.jinn.so/agents/add-an-agent.md) on its own. On **Only my own keys**, a workspace without a
working Gemini key can't transcribe, and indexing stops without telling anyone.

Add OpenAI if your team uses content actions or generates images, and Exa if you want
answers that draw on the web.

> [!TIP]
>
> For example: a team that records calls and asks questions about them needs a Gemini key
> and nothing else.

## Get a key

Every provider asks for the same four things, in roughly this order. Their guide in the table
above has the exact screens.

1. **Sign up or sign in** on the provider's site. Use an account your company controls, not a
   personal one, so the key doesn't leave with whoever created it.
2. **Set up billing.** Most providers won't serve a call until there's a payment method or a
   balance on the account. A key from an account without one looks fine on their site and
   fails in Jinn.
3. **Create the key.** Name it after the workspace — *Jinn – Marketing*, say — so you can tell
   later which key is which.
4. **Copy it straight away.** Most providers show a key once. If you close the window first,
   delete that key on their side and create a new one.

> [!NOTE]
>
> Some providers keep keys inside a project or a team. Create the key in the one that holds
> the billing, or the key exists but can't spend anything.

## Add the key to Jinn

Open **Settings** → **AI Providers**, find the provider and click **+** next to it
(**Add a key**). Paste the key and click **Check and save**. Jinn tests it with the provider before saving, so a key that doesn't work is never
stored.

If the test fails, Jinn shows what the provider said. The usual causes:

* **The key was copied with a space or cut short.** Copy it again from the provider.
* **The account has no billing yet.** Add a payment method or a balance there, then try again.
* **The key belongs to a different project or team** than the one with billing.

Once a key is saved it can't be read back, not by you and not by anyone at Jinn. Keep the
original wherever your team keeps passwords if you'll need it again.

## Keep a key working

A key that worked on day one can stop later, usually because the account ran out of money.
Jinn switches the key off, notifies owners and admins, and marks it **Inactive**.
[How your AI is powered](https://docs.jinn.so/workspace/ai-and-indexing.md) explains each reason and what to do.

A few habits keep that from happening:

* **Set a spending limit or budget alert** on the provider's side, so a busy month
  doesn't turn into a surprise invoice.
* **Turn on auto top-up** where the provider offers it, if you'd rather never hit an empty
  balance mid-meeting.
* **Use one key per workspace.** Usage shows up separately on the provider's side, and you can
  replace one without touching the others.
* **Rotate a key** by creating a new one at the provider, then **Replace this key** (the pencil next to the key) in Jinn,
  then deleting the old one at the provider. Nothing stops in between.

> [!WARNING]
>
> Never paste a key into a chat, a doc or a ticket. Anyone holding it can spend on your
> account. If one leaks, delete it at the provider first, then add a new one in Jinn.

## Where to go next

> [card] [How your AI is powered](https://docs.jinn.so/workspace/ai-and-indexing.md)
>
> Whose account the AI runs on, and what stops quietly.

> [card] [People and access](https://docs.jinn.so/workspace/people-and-access.md)
>
> Who reaches a project, and what they can do.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.