Openrouter.ai Now Supports Workspaces
Openrouter.ai has introduced Workspaces, a feature that allows users to organize projects, teams, and agents into isolated environments with separate settings for API keys, routing, guardrails, and observability. Each workspace operates independently with its own configurations while sharing account-level settings such as billing, logs, and organization management. The feature supports both individual and organizational use, enabling admin-controlled access and management across multiple environments.
Opening excerpt (first ~120 words) tap to expand
FeaturesWorkspacesCopy pageOrganize your projects, teams, and agents into separate environmentsWorkspaces let you organize your OpenRouter projects into separate environments, each with its own API keys, routing defaults, guardrails, and observability. Use them to isolate teams, projects, or deployment stages (e.g. staging vs. production) under a single account. Getting Started Your existing OpenRouter setup is already in a Default workspace. All of your API keys, guardrails, BYOK provider keys, routing policies, presets, plugins, and observability integrations are there. If you don’t need multiple workspaces, keep working as usual; nothing changes. For organizations, all members are automatically added to the Default workspace.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at OpenRouter Documentation.
Discussion
0 commentsMore from OpenRouter Documentation
