Read routes, orders, and driver activity. Replan the day as an approved step.
Connect OptimoRoute and ask about the day as it stands: which routes are planned, which orders are still open, what drivers reported from the field, and where a delivery landed. Reads come back right away. Changes like creating orders, updating driver parameters, or starting a new optimization run are previewed and held for approval first.
17 tools: 8 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed OptimoRoute 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 order, create or update orders, delete all orders, delete order, and more — is shown as a plan and requires approval by default, including the 5 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 OptimoRoute — 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.