Read Kaleido orgs, keys, and consortia. Change them as approved steps.
Connect Kaleido and your agent can answer questions about the blockchain estate without a console trip: which consortia exist, who holds memberships, what plan and billing the organization sits on, which API keys are live, and what event streams a node is publishing. Changes to keys, roles, and identity proofs run as previewed steps you approve first.
29 tools: 22 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Kaleido 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 add organization identity proof, create api key, delete api key, delete organization identity proof, and more. 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 Kaleido — 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.