nessieSite Agent Toolbox
How a digital employee is installed: the origin, the script, what it may do and who pays for its AI usage.
Give each product its own site agent
Site Agent Toolbox connects an agent to a web product your team uses. In Nessie Admin, you create an installation for that product, configure its connection and copy its own snippet into the site. You can add another installation for another product without sharing its connection, setup notes or site access.
What the agent can do
With a person signed in to the connected site and permission to act, the agent can inspect the current page, follow a visible link, fill a form and use its controls. It sees the page the person is on and uses the site’s existing permissions. Chat stays in the current browser session. Nessie does not store a transcript or run history for this page assistant.
An installation administrator can teach a reusable page procedure from the chat. Jev reviews every proposed memory. Information specific to a person or team is removed and reviewed again before a procedure can be saved. Teaching records describe page controls and steps, rather than customers or team content.
Your signed-in team pays for AI usage
People sign in with UnlikeOtherAI in Nessie’s chat and choose the team that pays for inference. Usage follows that team’s existing model and credit rules. An installation does not activate a subscription or trial; recurring installation fees and trials are not available yet.
The website receives the page-tool connection. The Nessie frame keeps sign-in, team selection and inference requests on Nessie’s origin.
Getting started
In Nessie Admin, open Site agents for the selected team, register the site’s exact secure origin and copy its installation script. Add that one script to the site to show the chat. Nessie uses the same integration in its Help drawer, where people can switch between page help and Chat.