Wachete
for LuumenAI
Read your Wachete monitors, then add or move watchers as approved steps
Connect Wachete and your agent can see every watcher in the account: what page it tracks, how often it checks, what it has recorded, and which notifications fired. Ask it to set up a new monitor on a vendor status page or reorganize folders, and it shows you the change first. Luumen authenticates with an API key.
The Wachete toolbox
11 tools: 6 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet crawler pagesRetrieves all pages monitored by a crawler watcher (portal monitor).
- ReadGet Data HistoryRetrieve history for a wachet (monitor).
- ReadGet folder contentRetrieves the contents of a Wachete folder, including subfolders and watcher tasks.
- ReadGet watcher by IDRetrieve complete watcher (monitor) definition by ID.
- ReadList notificationsRetrieves notifications from Wachete watchers.
- ReadList watchersList all monitoring watchers (tasks) configured in your Wachete account.
- WriteCreate or update folderCreate a new folder or update an existing folder in Wachete. Approval by default
- WriteCreate WatcherCreate or update a Wachete watcher to monitor web page changes. Approval by default
- WriteDelete folderPermanently deletes a folder along with all nested subfolders and watchers (monitoring tasks). Approval by default
- WriteDelete watcherDeletes a website monitoring watcher (task) by its unique ID. Approval by default
- WriteMove Items to FolderMove tasks (watchers) and folders to a specified destination folder. Approval by default
One prompt, start to finish
What a governed Wachete run looks like inside Luumen.
Questions
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 or update folder, create watcher, delete folder, delete watcher, 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 Wachete — 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.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Wachete to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.