Skip to main content
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

Add a key

Save a key in Profile, Secrets. The value goes from your browser straight to Proofable, so the agent never handles it. A connection has no tool that saves, lists or reads a key. A key typed into an AI app conversation is already 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.

Auth

How MCP sessions authenticate.

MCP tools

The 18 tools a connection serves.
Last modified on November 16, 2026