API key storage

In the new "Developer" tools, I'd love to see proper API key storage.  Honestly a lot of this can be accomplished with standard 1Password tools but I want to keep passwords separate from API keys whether by category or just plain feature separation into developer tools.  

It would be great if the browser extension could differentiate between an API key / token and a password.  Even if it can't it would be great to have an option to specify API vs password.

One key difference between passwords and API keys is that on one site you generally have a single login/password but with API keys you have one site and many keys usually with key/value pairs.

-- Example --

Type: API
Site: Anthropic
URL: console.anthropic.com

Key name:  Project A
Key value:  [32bit key value]

Key name:  Project B
Key value:  [32bit key value]

Key name:  Project C
Key value:  [32bit key value]

--- \ Example ---

Again, I understand you can make this work with existing passwords but API keys should be treated differently and have their own feature space.  This is a good feature for developers, and when evaluating a 1password for Business feature space an IT admin has to deal with a lot of API keys and it would be good to store them securely and easily be able to identify which API keys they may need to rotate.  

API keys could also be worked into Watchtower as API keys that have been leaked or exposed in data breaches.  

API keys are not just used within .env files, it could be website and even AI desktop tools like MCP  server settings.