Read Keen.io event schemas and cached datasets, then reactivate an access key on approval.
Connect Keen.io and your team can ask what event data exists without opening a browser. List every collection and its schema, inspect one property at a time, pull unique values, and review cached dataset definitions. When a revoked access key needs to come back, Luumen shows the key and the plan first, then reactivates it once you approve.
6 tools: 5 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Keen.io 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.
This connection exposes write actions such as unrevoke access key. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Keen.io — 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.