Multiple API keys, scoped per library

Issue as many API keys as you need and give each one exactly the reach it should have — read-only on one library, read-write on another, nothing on the rest. The keys settings page is rebuilt around managing many keys at once.

Read the docs →

What's new:

• Per-library access levels. Set each key to None, Read, or Write on a per-library basis, instead of one all-or-nothing grant.
• Many keys per organization. Create a separate key for each integration, agent, or environment.
• A faster keys page. Create a key inline without a modal, reveal its value on demand, and adjust a single library's access without touching the rest.
• One model everywhere. The same key and the same per-library access apply across REST, GraphQL, and MCP.