One real key, many ghost keys

Give each app, person, customer or AI agent its own ghost key for the same real key: each has its own rules, activity and kill switch. Choose Add ghost key on a key's page, or Use one already in Vallkey when you create a key. Nothing is pasted again.

• Replace once: a new real key under Real key (or PUT /real-keys/:id/secret) switches every ghost key at the same moment, after the safety hour, with a second admin when any of them is a production key.
• Kill one, or all: killing one ghost key leaves the others working. Kill all (POST /real-keys/:id/kill) stops every ghost key of the real key, for when the real key itself leaked.
• A new ghost key that may do more than every working ghost key of its real key starts after the safety hour, or after a second admin's approval, because nobody had to paste the real key to make it.
• Shared limits (Pro and up) count requests, money, AI tokens and AI budgets across all its ghost keys, on top of each one's own rules.
• Outer rules (Team and Business) say what any ghost key of it may ever do. Ghost keys made from code must stay inside them: with an API token, POST /real-keys/:id/ghost-keys, npx vallkey keys add --from <id>, or the MCP tool create_ghost_key.
• Pasted twice? The Keys page offers to link keys that hold the same real key, and a ghost key can move to another real key (after the safety hour).

Vallkey shows the provider's public prefix and the last four characters of a real key, such as sk_live_…9xQa, so you can tell them apart. The rest is never shown again.