AGENTIC COMMONSAI industry briefings

繁中EN

TopicAI Safety & SecurityPublished

All English articles

OpenRouter management keys go scoped and read-only

Summary: On November 16, 2026, OpenRouter announced that management keys no longer have to come with full admin access to a whole organization. A key can now be read-only, limited to one workspace, or both, and the feature is available to every organization on every plan. If you run agents or automation against OpenRouter’s management API, this changes how much damage a leaked or buggy key can do — and it costs almost nothing to adopt.

Two settings, fixed at creation

Every new management key carries two choices, made when the key is created. Scope sets where it works: one workspace or the whole organization. Access level sets what it can do there: read-only or read and write.

The scope enforcement is straightforward: if a request names another workspace, or any resource belonging to one, OpenRouter refuses access. Inside its own workspace, the key can manage API keys, members, guardrails and guardrail policies, your own provider keys, observability destinations, and presets, and it can read the workspace’s budgets, activity, and analytics.

Access level applies to workspace keys and organization keys alike. A read-only key can call the read routes its scope allows, including analytics queries; anything that would create, change, or delete something returns an error. That fits monitoring agents watching activity, cost dashboards pulling usage, and audit scripts listing keys and guardrails — tools that only need to look.

The two settings combine into four useful shapes, and OpenRouter’s own examples map them to real jobs: an agent that creates and rotates one team’s API keys gets a read/write workspace key; a usage dashboard for that team gets a read-only workspace key; an organization-wide audit or cost tool gets a read-only organization key; and anything creating workspaces or setting budget limits keeps a read/write organization key.

What stays out of reach

Workspace-scoped keys hit a deliberate wall at the organization boundary. Budget limits, credits, and organization settings remain with Organization Admins — a team can automate everything inside its workspace and still cannot raise its own workspace budget. Setting a workspace budget, creating or deleting workspaces, managing organization members, and private endpoints all still need an organization key, which works the way it always has.

This is the continuation of a direction we looked at when OpenRouter launched workspaces: organizations split into per-team workspaces while admins govern what everyone shares. Scoped keys are the automation-side half of that model.

Keys can’t be edited, only replaced

One trade-off is worth planning for: both settings are immutable after creation. A key cannot gain access later — to change scope or access level, you create a new key and delete the old one. That prevents quiet privilege creep, but it means any change to what your automation needs is a rotate-and-swap, not a toggle in a settings panel.

Day-to-day usage is unchanged. Tools call the management API with the key as a Bearer token:

curl https://openrouter.ai/api/v1/keys \
  -H "Authorization: Bearer $MANAGEMENT_KEY"

To create a key, open the workspace, go to Keys, and select the Management keys tab; Workspace Admins can create keys for their own workspace, and Organization Admins use the Management API Keys page for organization-wide keys.

Auditing what you already hold

The announcement includes a review path for existing keys: open Security settings, go to Key safety, open Filter keys, and select Show management keys. Each active key is listed with its owner, last use, and expiration — which is exactly what you need to inventory before rotating.

Our take: Act now if you run agents or CI against OpenRouter’s management API, especially across multiple workspaces. The migration is an afternoon: audit your active keys, mint a scoped replacement per job, swap the bearer token, delete the original. It’s reversible, needs no new infrastructure, and carries no plan-gating — the assumption behind the urgency is that management keys are bearer tokens, so until you rotate, one leaked key reaches every team’s workspace. Solo builders with a single workspace and one key used for occasional manual tasks can safely ignore this; there is little blast radius to contain. One condition that should slow you down: the sources don’t say what a leaked read-only key can still see — which read routes return analytics or member data — so weigh that residual exposure before deciding a read-only key is safe to hand a third-party dashboard. And if your automation must set budgets or create workspaces, scoped keys can’t cover those jobs anyway.

Sources

AGENTIC COMMONSOperated by PHLEGON LABS
ShareXEmail
Support us

Related reading

  1. Cloudflare Workers Granular Authorization for Agents

    Teams should scope agent tokens per Worker: four roles limit access, while route changes still require separate zone permission.

    Cloudflare

  2. Zero Data Retention: Enforcing Provider-Side Privacy on AI API Calls

    ZDR is a routing control that stops AI providers from storing prompts and responses—but only if you enforce it per request.

    AI API

  3. OpenRouter In-Region Routing: Decryption and Inference

    Residency-bound teams should use regional routing; unavailable local models return 404 instead of routing elsewhere.

    OpenRouter