Validate numbers, emails, addresses and IPs, then send a verification code
Neutrino gives your agent a set of checks it can run mid-investigation: is this mobile number live and on which network, is this email deliverable, is this IP on a blocklist, what address sits at these coordinates. Reads come back right away. Sending a verification code by SMS is a write, so it is previewed and approved before it goes out. Luumen connects with an API key.
24 tools: 23 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Neutrino 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 sms verify. 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 Neutrino — 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.