OpenRouter management keys add read-only and workspace scoping
Understand this story
OpenRouter has added two new settings to Management Keys—"scope" and "access level"—allowing keys to be restricted to a single workspace and set to read-only. The two settings combine into four key types, which cannot be modified after creation; to adjust them, you must create a new key and delete the old one. Read-only keys can only view API keys, activity, and usage; read-write keys can also create, update, and delete API keys. OpenRouter says the feature is now available to all organizations on all plans. Setting workspace budgets, creating or deleting workspaces, managing organization members, and private endpoints still require organization keys, whose usage is unchanged.
AI overview based on source reports · Updated 8 hr ago
Coverage timeline
Follow the coverage to explore different perspectives.
- OpenRouter AnnouncementsTighter Access Controls for Management Keys
OpenRouter management keys can now be scoped to a single workspace or the whole organization and set to read-only or read/write, with both settings fixed at creation. Workspace Admins can create keys for their own workspace, while organization-wide actions like setting budgets, creating workspaces, and managing organization members still require an organization key. Read-only keys can call read routes including analytics queries, and any create, change, or delete request returns an error.
Activity for this story
- Current comparable activity
- 3
- Peak comparable activity
- 3Nov 18 02:00
- Change in the past 24 hours
- –
Trends compare the same fully observed participants, which may cover fewer participants than current activity. Move the pointer or tap the chart to inspect hourly activity; use the left and right arrow keys with a keyboard.