Read HoneyHive runs, events, and datasets, then change them as approved steps
Connect HoneyHive and your agent can read the evaluation history behind an AI application: runs and their metrics, event trees for a single session, datasets, and configurations. When something needs to change — a failing case added to a regression dataset, a new configuration, a batch of logged events — the agent shows the plan first and waits for your approval. Authentication is by API key.
42 tools: 19 read, 23 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Honeyhive 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 — add datapoints to dataset, batch create datapoints, create batch model events, create batch tool events, and more — is shown as a plan and requires approval by default, including the 2 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 Honeyhive — 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.