Check Authyo sessions and tokens, then revoke or send codes on approval
Connect Authyo and your agent can answer session questions on the spot: whether a token is still valid, and which user identity sits behind it. When something needs to change — revoking a session, verifying an OTP, sending a code or an order notification — the agent shows the plan first and waits for your approval before it runs. Luumen authenticates with an API key.
5 tools: 1 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Authyo 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 — revoke session, send order notification, send otp, verify otp — 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.
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 Authyo — 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.