Inspect AI21 Studio assistants and routes, then change them as approved steps
Connect AI21 Studio and your team can ask about the assistants, routes, and storage configurations behind your live features without opening the console. Luumen reads assistant definitions and batch job status on request, and answers immediately. Changes — a new route, a new assistant, a deleted demo — are previewed first and go out as approved, audited steps.
57 tools: 32 read, 25 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Studio By Ai21 Labs 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 — create aftersales parts classification batch, create assistant route, create assistant, create assistant plan, and more — is shown as a plan and requires approval by default, including the 6 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 Studio By Ai21 Labs — 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.