Read your BigML resources, then rename or retag a source as an approved step
Connect BigML with an API key and Luumen can read across your account: projects, sources, external connectors, configurations, and the long lists of anomaly detectors, associations, batch predictions, centroids, and projections. Ask what exists and get an answer. When something needs to change, Luumen shows the edit first and waits for your approval.
45 tools: 41 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Bigml 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.
This connection exposes write actions such as create external connector, create project, delete project, update source. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Bigml — 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.