Keys belong to the workspace
- Keys are registered to the workspace, not to a person. Add once; every Flow in the workspace uses it.
- Values are masked on save and never shown again. To change one, overwrite it with a new value (Replace).
- Keeping keys per workspace splits usage cleanly on the provider’s own dashboard.
Adding a key
Settings → Providers lists every supported provider under External API keys, each with its key slot:
Press Add key on a provider’s row, paste the key (input is masked), and save. A connected provider shows a connected badge with Replace / Remove.
Keys can also be set from the CLI — see
nora providers.
Removing a key
Remove deletes the key. Anything that used that provider fails on its next call until a new key is added.Billing
External LLM token costs are billed by the provider on your key; they never appear on Nora’s invoice. Nora’s own usage fees are separate; see Plans. If you route to an in-house endpoint instead (see Internal resources), there’s no external token cost at all.Related
Ask AI
Hosted routing uses these keys.
Internal resources
Register in-house OpenAI-compatible endpoints instead.