Skip to main content
Nora runs your Agents against models from multiple providers (OpenAI, Anthropic, Google, and more). Each provider needs a per-workspace API key. providers is the CLI for managing them.

Commands

providers list

Prints all supported providers and their status:
  • openai: configured — key set.
  • anthropic: not configured — no key.
  • google: configured.
Add --json for structured output.

providers set

Flags:
  • <provider> (positional, required) — provider ID.
  • --stdin — read key from stdin. Preferred.
  • --env <var> — read from environment variable. Preferred for CI.
  • Positional key — literal. Least preferred (lands in shell history).
Stored keys are encrypted at rest and never returned via any API — the CLI can never read them back. Rotate by re-running set with a new key. Old key is replaced immediately.

providers delete

Removes the stored key. Any Flow using this provider’s models will fail until you set a new key. Confirmation required unless --yes passed.

providers check

For a specific Flow, reports:
  • Which providers the Flow’s Agent blocks reference.
  • Which of those providers have keys configured.
  • Any gaps.
Great as a pre-publish check — catches “we changed models but forgot to add the key” before ship. Example output:
Add --json for scriptable output — CI can gate on it.

Recipes

Set keys from environment in a bootstrap script

Fits well in a workspace setup runbook.

CI: fail if any provider is missing for a Flow

Rotate a key with grace

Rotation is atomic — new key is used from the next call. Existing in-flight runs finish on the old key. Watch traces for auth failures over the next few minutes as a sanity check:

Migrate keys between workspaces

Keys are workspace-scoped — each workspace has its own.

Providers and cost

Provider keys are billed by the provider directly (OpenAI, Anthropic, …) unless you’re on a Nora-managed model tier. The Nora platform’s own billing is separate — see nora billing. Use per-workspace keys for cost attribution: your OpenAI dashboard shows spend by API key, so a per-workspace key lets you split cost per team or per environment.