Lyzr
for LuumenAI

Inspect Lyzr agents, schedules, and simulation issues, then change them with approval

Connect Lyzr and your team can see what the agent fleet is actually doing: which Agent Studio agents exist, how they are configured, what schedules run them, and which performance or Responsible AI issues have piled up. Reads answer right away. Changes like creating an agent, setting its status, or adding a cron schedule are previewed and held for approval first.

The Lyzr toolbox

22 tools: 13 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet AgentReturn the current configuration and status of one Agent Studio agent by ID.
  • ReadGet Knowledge BaseReturn one Lyzr Knowledge Base configuration by its known RAG configuration ID.
  • ReadGet Simulation OverviewReturn aggregate Agent Simulation counts and average evaluation pass rate for the connected workspace.
  • ReadList AgentsReturn all Agent Studio agents owned by the connected API key, including IDs needed by lifecycle and inference tools.
  • ReadList Agent SchedulesReturn one page of agent cron schedules, optionally filtered by user, agent, or active state.
  • ReadList Agent Simulation IssuesReturn recent performance, error, and Responsible AI issues across monitored agents, optionally filtered by resolution and severity.
  • ReadList RAI PoliciesReturn Responsible AI policies owned by the authenticated user, including policy IDs and enabled guardrail configuration.
  • ReadList SuperFlow ExecutionsReturn one page of SuperFlow execution records, optionally filtered by workflow and execution status.
  • ReadList SuperFlow WorkflowsReturn all SuperFlow workflow definitions accessible to the connected API key, including workflow IDs and graph data.
  • ReadList Voice AgentsReturn saved Voice agents accessible to the connected organization, including IDs used to filter transcripts.
  • ReadList Voice TranscriptsReturn one page of accessible Voice call transcripts, optionally filtered by agent, session, organization, or date range.
  • ReadRetrieve KnowledgeRetrieve relevant documents from a known Lyzr Knowledge Base using configurable basic, MMR, hypothetical-document, or time-aware retrieval.
  • ReadSearch MemoriesSemantically search stored memories for one owner, within one session or across that owner's sessions, using Lyzr's hybrid vector and BM25 retrieval.
  • WriteAdd Memory MessagesStore a batch of conversation messages in Lyzr Memory for an owner, session, and optional agent, with optional synchronous fact extraction. Approval by default
  • WriteChat With AgentSend a message or message history to an active Agent Studio agent and return its synchronous inference response for a session. Approval by default
  • WriteClear Memory SessionPermanently clear messages and memories for one explicit owner and session in Lyzr Memory. Approval by default
  • WriteCreate AgentCreate a single-task Agent Studio agent with an LLM provider, model, instructions, and optional tool configuration. Approval by default
  • WriteCreate Agent ScheduleCreate a cron schedule that runs one Agent Studio agent with a message in a specified timezone. Approval by default
  • WriteDelete AgentPermanently delete one Agent Studio agent by ID. Approval by default
  • WriteDelete Agent SchedulePermanently delete one agent cron schedule and remove its associated scheduler job. Approval by default
  • WriteEvaluate Text With RAI PolicyApply one owned Responsible AI policy to text and return processed text, block decisions, warnings, detections, and redactions. Approval by default
  • WriteSet Agent StatusActivate or deactivate an Agent Studio agent. Approval by default

One prompt, start to finish

What a governed Lyzr run looks like inside Luumen.

Questions

How does LuumenAI connect to Lyzr?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Lyzr on its own?

Read actions answer immediately. Anything that writes — add memory messages, chat with agent, clear memory session, create agent, and more — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

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.

Is there an audit trail?

Every call to Lyzr — 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.

Put Lyzr to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.