Tighter Access Controls for Management Keys
OpenRouter added scoped management keys, so a management key no longer has to carry full admin access to your whole organization. Each key now gets two settings: a scope (one workspace, or the whole organization) and an access level (read only, or read and write).
A workspace-scoped key only works inside its own workspace. If a request names another workspace, or a resource that belongs to one, OpenRouter refuses it. Inside that workspace, the key can manage API keys, members, guardrails and guardrail policies, your own provider keys, observability destinations, and presets. It can read budgets, activity, and analytics, but budget limits, credits, and organization settings stay with Organization Admins. Setting a workspace budget, creating or deleting workspaces, managing organization members, and private endpoints still need an organization key.
Read-only keys can call the read routes their scope allows, including analytics queries. Any request that would create, change, or delete something returns an error. That suits a cost dashboard, a monitoring agent, or an audit script that only needs to look.
To make one, open a workspace, go to Keys, pick the Management keys tab, and click New management key. Name it, choose an expiration, and set the access level. Workspace Admins can create keys for their own workspace, and Organization Admins can create them for any workspace. Organization-wide keys come from the Management API Keys page. Agents use the key as a Bearer token on the management API, the same way as before. Scope and access level are fixed when you create the key, so changing either means creating a new key and deleting the old one.
It's available to every organization on every plan.