Adding your OpenRouter or Composio key to run for free
Bringing your own provider API key is the way to use the full HIIE engine at $0. This article covers where to add account-level keys and what happens after you do.
Where to add keys
Account-level BYO keys are OpenRouter and Composio, stored in a per-user encrypted credential vault. You manage them from the Connections section's Credentials tab. Saving adds the key (encrypted at rest); deleting removes it.
What you'll see back
For security, the vault never returns your raw key to the browser. After saving, you only see a masked status showing the last few characters. Keys are read server-side only — they're encrypted with AES-GCM at rest and never logged or sent to the client.
What changes after you add an OpenRouter key
An active OpenRouter BYO key flags your account as "byo". From then on:
- Your runs are unmetered — they show as $0 / free in your ledger.
- They do not draw down any managed credit balance or monthly capacity.
- Free-tier managed limits (the monthly inference ceiling, the programmatic sub-cap) don't apply to you, because your own key carries the cost.
Composio keys
A BYO Composio key runs integrations under your own Composio org for maximum isolation. As with OpenRouter, only a masked hint is ever shown and the full key never reaches your browser.
You can add or remove keys at any time; switching back simply re-enables managed metering.