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

# Provider API keys

> Use your own OpenAI, Deepgram, or Cartesia account for personas and model graders.

Open **Settings → Provider API Keys** to manage keys for your organization.
These keys pay for calls to model providers. The separate **API keys** page
creates tokens that authenticate scripts and integrations to Egma.

An organization admin can add, replace, or remove one key for each supported
provider: OpenAI, Deepgram, and Cartesia. Other members can see which providers
have a saved key and its masked ending.

Manage these settings through a browser session or an organization API key.
A project API key cannot read or change organization provider keys, even when
its owner is an admin.

## Add or replace a key

1. Choose **Add key** beside the provider, or **Manage key** to replace one.
2. Paste the provider's API key and choose **Save key**.
3. Select your supported models in the persona or model grader's settings.

The key applies across projects in the organization. Model choices remain
specific to each project's persona or grader settings, including predefined
personas and graders. Adding a key does not add unsupported models to the
catalog.

New work uses the saved key for that provider. Calls already in progress keep
the key they started with. If the saved key fails, Egma reports the provider
failure and does not switch to a default key.

## Inference credit on Egma Cloud

A call that uses your provider key does not deduct Egma inference credit.
Your provider bills its account directly. Usage still appears in Egma's usage
and cost records.

Funding is separate for each provider. For example, an OpenAI key pays for
OpenAI calls; Cartesia calls still use Egma credit unless you also add a
Cartesia key. Your Egma plan fee, usage allowances, and applicable voice
overages remain in effect.

Choose **Manage key → Remove key** to return a provider to the default keys.
The confirmation explains that new calls on Egma Cloud will use inference
credit again. Removing a key does not change who paid for earlier calls.

## Self-hosted deployments

Organization keys take precedence over the deployment's
[provider environment settings](/configuration/environment-variables#model-provider-credentials).
The API and grader need the same generated `EGMA_ENCRYPTION_KEY` to open saved
keys. Keep the platform configuration with the database backup.