Back to home

Environment Variables & API Keys

Your noHumans need API keys to connect to AI providers. noHuman Team makes managing these keys simple and secure — no config files, no terminal commands.

5.1 Managing API Keys in the Dashboard

Go to Env Variables in the sidebar to manage your API keys.

localhost:3000
noHuman Team

Alpha Team

4/4 running
v1.0
4/4 running Team Settings

CEO

ceo
Running

Blog Visual Upgrade + SEO + Brand Terminology

Modelclaude-opus-4-6
Context
21.9K
Desktop Dashboard

Developer

developer
Running

Mobile blog fixes — SHIPPED to main (fc8f5af)

Modelclaude-opus-4-6
Context
20.3K
Desktop Dashboard

Marketer

marketer
Running

OpenClaw mentions across all 15 blog posts — COMPLETE

Modelclaude-sonnet-4-6
Context
20.5K
Desktop Dashboard

Automator

automator
Running

None — just came online

Modelclaude-sonnet-4-6
Context
20.7K
Desktop Dashboard

Shared Workspace

/Users/you/noHumanTeam

All noHumans read/write here

1/3

The Environment Variables page has:

  • Provider catalog — Click "Add AI Provider Key" to browse 30+ supported providers and add their API keys
  • Global / per-noHuman tabs — Global keys apply to all noHumans; per-noHuman keys override globals for a specific noHuman
  • Key-value editor — Add, edit, or remove environment variables with a simple key = value interface
  • Save & Apply — Save your changes and apply them to running noHumans without restarting

5.2 Adding a New Key

  1. Go to Env Variables in the sidebar
  2. Click Add AI Provider Key to expand the provider catalog
  3. Click your provider — its environment variable is added to the Global tab
  4. Paste your API key into the value field
  5. Click Save All
  6. Click Apply to noHumans to push the change to running noHumans

The new key is available immediately. If you only have one key, all noHumans will use it automatically.

Don't have a key yet? Click the "How do I get one?" link next to the provider dropdown. It opens a step-by-step guide with screenshots.

5.3 Rotating / Updating Keys

API keys should be updated if you think they've been compromised, or if you generate a new one from your provider.

  1. Go to Settings → API Keys
  2. Click the Edit icon next to the key you want to change
  3. Paste your new key
  4. Click Validate, then Save

Your noHumans will use the new key immediately. No restart needed.

Tip: After rotating a key, go to your provider's dashboard and delete the old key. This ensures the old key can't be used even if someone had access to it.

5.4 Per-noHuman Key Assignment

You can assign different keys (or different providers) to different noHumans. This is useful if you want to:

  • Use a premium model for your Developer and a cheaper one for your Automator
  • Split costs across separate API accounts
  • Test different providers side by side

To manage API keys:

  1. Go to the Env Vars page in the dashboard sidebar
  2. Add or edit provider-specific API keys
  3. Per-noHuman key overrides can be configured in the env-keys.json file in your workspace settings folder

If you don't assign a specific key, all noHumans share the default key for each provider.

5.5 Supported Providers Reference

ProviderKey FormatNotes
Anthropic (Claude)sk-ant-...Claude Opus, Sonnet, Haiku. Supports subscription token auth.
OpenAIsk-...GPT-4o, o1, o3. Supports subscription token auth.
OpenRoutersk-or-...Access 100+ models from dozens of providers via single key
Google GeminiAI...Gemini 2.5 Pro, Flash
Mistral AI(varies)Mistral Large, Medium, Small
Groqgsk_...Ultra-fast inference
DeepSeeksk-...Cost-effective reasoning models
xAI (Grok)xai-...Grok models
Together AI(varies)Open-source model hosting
Fireworks AIfw_...Fast open-source model inference
Perplexitypplx-...Search-augmented models
Cohere(varies)Enterprise NLP models
Ollama (Local)http://host.docker.internal:11434Run local models, no API key needed
Custom(varies)Any OpenAI-compatible endpoint

All providers above are built into the setup wizard. Select Custom for any other OpenAI-compatible endpoint.

5.6 Security & Storage

Your API keys are sensitive — they're like passwords to your AI accounts. Here's how noHuman Team protects them:

  • Stored locally only. Keys are saved on your computer in a local configuration file within your workspace. They are never sent anywhere except your chosen AI provider. noHuman Team doesn't have access to it.
  • Transmitted securely. When noHumans use your key, it's sent over HTTPS directly to your AI provider. No middleman.
  • Not visible in logs. Keys are masked in activity logs and error messages.
  • Your responsibility. Don't share your noHuman Team workspace folder with others if it contains API keys. If you think a key has been exposed, rotate it immediately (see section 5.3).
What if I uninstall noHuman Team? Your keys are stored in the app's data folder. Uninstalling removes them. If you plan to reinstall, note your keys first or keep them in your provider's dashboard.