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

# Encrypted secrets

> Save an API key once. Your assistants, jobs, agents, and connected AI apps use it through Proofable, and the value is never shown again.

Give the agent the tool. Keep the credential.

A secret is an API key or other credential you save on your Proofable Profile. Proofable encrypts it and uses it for you when a call needs it. The value never comes back to you, to the AI app you are using, or to an agent.

## Where a saved key works

| Where | How the key is used |
| - | - |
| **Proofable assistant** | Pick the provider in the assistant. Proofable calls it with your saved key instead of the included model access. |
| **Jobs** | A job that runs on your provider uses the same saved key for its model calls. |
| **Agents you create** | Bind a secret to an agent. The agent uses it through Proofable and never reads it. |
| **MCP clients** | A signed-in connection can list your saved keys (names only), remove one, and call a provider with one through `proofable_capability_call`, which returns the provider's answer. |

## Add a key

Save a key in [Profile → Secrets](https://proofable.me/profile?tab=secrets) or through the [product API](https://docs.proofable.me/reference.md). The value goes from your browser straight to Proofable, so the agent never handles it. MCP tools have no way to save a key, because a key typed into an AI app's conversation has already been disclosed to that app.

Name a key after its provider, such as `OPENAI_API_KEY` or `ANTHROPIC_API_KEY`, so Proofable knows which provider it belongs to. For any other provider, add a `provider:<id>` tag when you save it.

## Common questions

**Can I see a saved key again?** No. After saving, you see its name, type, and when it changed. To change it, save a new value.

**Who can read the value?** No response from Proofable contains it. The service decrypts it only at the moment it makes a call you asked for, and sends it only to that provider.

**How is it stored?** As a private encrypted record on your profile, sealed with AES-256-GCM.

**How do I rotate a key?** Save a new value under the same name. The new value replaces the old one, and the old record is revoked.

**What does revoke do?** It permanently deletes the stored record. Database backups that still contain it expire within seven days. If a key was exposed, also revoke it at the provider.

**Does Proofable use its own keys?** The included assistant tiers use Proofable's model access. When you add your own key for a provider, your requests to that provider use your key.

> [card] [Auth](https://docs.proofable.me/mcp/auth.md)
>
> How MCP sessions authenticate.

> [card] [MCP tools](https://docs.proofable.me/mcp/tools.md)
>
> List, remove, or call a provider with a saved key.


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