What are OpenRouter Workspaces?

OpenRouter Workspaces are separate environments used to organize projects within a single account. Each workspace has its own independent API keys, member access controls, and routing defaults. This allows developers to isolate staging and production environments or manage multiple client projects with specific guardrails and observability settings for each.

How does billing work for multiple OpenRouter Workspaces?

Billing and credits are managed at the account level rather than per workspace. All usage across every workspace is consolidated into a single bill. While individual workspaces can have their own API keys and routing policies, they all draw from the same shared pool of credits and follow the organization top-level data privacy policies.

Can I manage OpenRouter Workspaces programmatically?

Yes, OpenRouter provides a management API that allows you to create and manage workspaces programmatically. You can use management keys, which operate at the account level, to perform administrative actions across all workspaces. This is useful for teams that need to automate environment setup or manage large-scale deployments across multiple projects.

What settings are shared across all OpenRouter Workspaces?

Certain settings remain global at the account level, including billing, credits, and organization-wide data privacy policies. While workspaces can implement more restrictive guardrails, they cannot override the account-level ceiling for data policies or allowed providers. Activity logs and management API keys are also shared across the entire organization for centralized oversight.

Who has access to OpenRouter Workspaces?

Organization admins have full administrative permissions across all workspaces, including the ability to create or delete them. Regular members can belong to multiple workspaces and manage their own API keys within them. By default, all organization members have access to the Default workspace, but access to additional workspaces is controlled by admins.

OpenRouter Launches Workspaces to Segment API Keys and Routing Policies

LLM

Enterprise AI

AI Agent

Performance

Published Apr 24, 2026

OpenRouter Launches Workspaces to Segment API Keys and Routing Policies

OpenRouter, a unified API platform for accessing hundreds of LLMs, launched Workspaces to organize projects into separate environments. Each workspace acts as an independent container with its own scoped API keys and observability (monitoring system health and performance). This follows the platform's recent expansion into specialized tools like the reranker API.

As AI development shifts to complex agentic workflows, global API keys become a security bottleneck. Workspaces solve this by extending the platform's routing optimization to a per-project level—letting you prioritize cost for testing while enforcing high-quality tool-calling for production. This isolation prevents configuration changes in one project from impacting others.

You can create workspaces via the dashboard or the Management API. Existing configurations have been migrated to a Default workspace. While billing remains centralized, this update adds to the management of autonomous agents by allowing you to apply specific guardrails within those constraints.

Read the full update →

Frequently asked questions

What are OpenRouter Workspaces?: OpenRouter Workspaces are separate environments used to organize projects within a single account. Each workspace has its own independent API keys, member access controls, and routing defaults. This allows developers to isolate staging and production environments or manage multiple client projects with specific guardrails and observability settings for each.
How does billing work for multiple OpenRouter Workspaces?: Billing and credits are managed at the account level rather than per workspace. All usage across every workspace is consolidated into a single bill. While individual workspaces can have their own API keys and routing policies, they all draw from the same shared pool of credits and follow the organization top-level data privacy policies.
Can I manage OpenRouter Workspaces programmatically?: Yes, OpenRouter provides a management API that allows you to create and manage workspaces programmatically. You can use management keys, which operate at the account level, to perform administrative actions across all workspaces. This is useful for teams that need to automate environment setup or manage large-scale deployments across multiple projects.
What settings are shared across all OpenRouter Workspaces?: Certain settings remain global at the account level, including billing, credits, and organization-wide data privacy policies. While workspaces can implement more restrictive guardrails, they cannot override the account-level ceiling for data policies or allowed providers. Activity logs and management API keys are also shared across the entire organization for centralized oversight.
Who has access to OpenRouter Workspaces?: Organization admins have full administrative permissions across all workspaces, including the ability to create or delete them. Regular members can belong to multiple workspaces and manage their own API keys within them. By default, all organization members have access to the Default workspace, but access to additional workspaces is controlled by admins.