Read your contracts, watchers, and webhooks, then change them with approval
Connect Starton and Luumen can see the smart contracts in your project, the templates available to deploy from, and every watcher and webhook listening for on-chain events. Ask what a watcher points at or which webhooks are still live, and you get an answer from the API. Changes — uploading a file to IPFS, deleting an event watcher — are previewed and approved first.
6 tools: 4 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Starton 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 delete smart contract event, upload file to ipfs. 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 Starton — 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.