Read GPTBots agents, conversations, and credit use, then open a new conversation
Connect the GPTBots agent behind your Singapore Agent API Key and Luumen can answer questions about it directly: which knowledge bases and documents are attached, what conversations ran in the last week, what credits each one consumed, and which attributes are set on a given user. When you need a live conversation opened or a message sent to the agent, Luumen previews the call and waits for your approval.
12 tools: 10 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed GPTBots 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 conversation, send message — is shown as a plan and requires approval by default, including the 1 action 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 GPTBots — 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.