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

# Stored API Keys

> Store and manage API keys for AI providers and third-party services

Stored API Keys let you save your API keys once and reuse them across all your flows. Instead of pasting a key into every node, you select a stored key from a dropdown.

## Supported Providers

| Provider           | Key Prefix                     |
| ------------------ | ------------------------------ |
| **OpenAI**         | `sk-...`                       |
| **Anthropic**      | `sk-ant-...`                   |
| **Google AI**      | `AI...`                        |
| **Mistral**        | --                             |
| **Azure OpenAI**   | --                             |
| **Stripe**         | `sk_test_...` or `sk_live_...` |
| **Resend**         | `re_...`                       |
| **Custom / Other** | Any key format                 |

## Adding a Key

<Steps>
  <Step title="Open Keys & Connectors">
    Go to **Settings > Keys & Connectors**. The **Stored API Keys** section lists all your saved keys.
  </Step>

  <Step title="Click Add API Key">
    Click the **Add API Key** button in the top-right corner of the section.
  </Step>

  <Step title="Fill in the details">
    * **Name:** A label you'll recognize later (e.g. "Production OpenAI Key").
    * **Key Type:** Select the provider from the dropdown.
    * **API Key:** Paste your key. The field is masked by default.
  </Step>

  <Step title="Store the key">
    Click **Store Key**. The key is encrypted and saved. Only the last four characters are shown for identification.
  </Step>
</Steps>

## Deleting a Key

Hover over a key in the list and click the **trash icon**. Confirm deletion in the dialog. Any flows that reference the deleted key will need to be updated with a new key.

## Using Stored Keys in Nodes

Nodes that require an API key, such as **Agent**, **Email (Resend)**, and **Stripe**, include a key selector with two modes:

* **Stored:** Pick a saved key from a dropdown. If you have stored keys matching the node's provider, this mode is selected automatically.
* **Manual:** Paste a key directly into the field, as usual.

You can switch between modes at any time. When you select a stored key, the node references it by ID so the actual secret is never embedded in your flow configuration.

<Tip>
  When you have stored keys available, nodes default to **Stored** mode so you can get started faster.
</Tip>

## Security

* Keys are **encrypted at rest** and never exposed in the browser after storage.
* Only the **last four characters** are displayed for identification.
* Keys are resolved server-side at execution time. They are never sent to the client or included in exported flow data.