logo
AgentLed

API Keys

Generate and manage workspace API keys for MCP connections and API access. Keys start with wsk_ and are scoped to a single workspace.

Generating a Key

1.Sign in at agentled.app

2.Open Workspace Settings > Developer

3.Click Generate API Key

4.Copy the key immediately — it is only shown once

Keys follow the format wsk_xxxxxxxxxxxxxxxx. Each key is scoped to the workspace where it was created.

Using Your Key

Environment Variable (recommended)

export AGENTLED_API_KEY=wsk_...

Both the CLI and MCP server read this variable automatically. Add it to your shell profile (~/.bashrc, ~/.zshrc) for persistence.

MCP Client Flag

Pass the key inline when registering the MCP server:

claude mcp add agentled \
  -e AGENTLED_API_KEY=wsk_... \
  -- npx -y @agentled/mcp-server

CLI Login

The CLI setup wizard handles authentication automatically:

# Interactive setup — opens browser, creates account, saves key
npx @agentled/cli --setup

# Or log in manually
agentled auth login

Rotating Keys

To rotate a key, generate a new one from the Developer settings, update your environment or MCP config, then delete the old key. Active connections using the old key will stop working immediately.

1.Generate a new key in Workspace Settings > Developer

2.Update AGENTLED_API_KEY in your environment and MCP configs

3.Verify the new key works, then delete the old key from the dashboard

Security Best Practices

  • •Never commit keys to source control. Use environment variables or a secrets manager.
  • •Add .env to your .gitignore. Prevent accidental exposure of local env files.
  • •Rotate keys periodically. Generate a new key, update configs, then revoke the old one.
  • •Use separate keys per environment. Keep development and production workspaces isolated.

Next Steps