The Credentials vault: storing your BYO Composio and OpenRouter keys
The Credentials tab is your per-user bring-your-own (BYO) key vault. It holds your own Composio and OpenRouter API keys, encrypted at rest, so you can run on your own accounts.
What it stores
The vault accepts two account-level BYO keys: a Composio key and an OpenRouter key. They're saved encrypted (AES-GCM) in HIIE's data store and read only on the server.
Privacy and masking
Your keys are never sent back to the browser. After you save a key, the vault shows only a masked hint of it (the last few characters; the key itself is never returned). This means HIIE can use the key on your behalf server-side without ever exposing it to the client.
Why use BYO keys
When you supply your own OpenRouter key, your managed-inference runs become unmetered — they show as free and don't draw down your account's managed capacity. In other words, bringing your own key makes those runs free on your own account. Supplying your own Composio key also gives your integrations the highest isolation tier, running under your own Composio organization.
Managing keys
From the Credentials tab you can save a key (stored encrypted), check its masked status, and remove it. Because the raw key is never displayed again after saving, keep your own copy if you need it elsewhere.
Related
To see which Composio key mode your account is actually resolving to — your BYO key, a dedicated project key, or the shared managed key — check the Environment tab, covered in its own article.