Look up licenses and activations, then change them as approved steps
Keyzy holds the licenses your customers run on. Connect it and you can ask about a serial in plain language: who owns it, which products it covers, which devices are activated. When something needs to change — a stale activation turned off, a term extended, a license moved to a new SKU — Luumen shows the plan first and waits for your approval. Authentication is by API key.
14 tools: 4 read, 10 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Keyzy run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete activation, delete license, download encrypted license file, register dealer license, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Keyzy — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.