Skip to main content
Ask Zach is OVRSEA’s own assistant, already inside Hermès. It needs no integration and no developer: anyone who can sign in to Hermès can use it. It is listed here because it is the third way an agent reaches an account, and because the people you build for are likely already using it. It is a single conversation in the Hermès header. There is no separate console: the user types the question in their own language, and Zach answers against that account’s real data.

​
How it relates to the API

Ask Zach is not a separate permission model. It resolves what the user can see and change from their own Hermès session — the same server-side checks the equivalent Hermès screen runs. Note that this makes it person-scoped, like the MCP server and unlike a REST token, which is issued for the account rather than for one colleague. It can perform all of the agent actions. Before any of them it states what it is about to change and waits for the person to agree: on a card for the most common actions, in the conversation for the rest. That is a confirmation step in the assistant rather than a second authorisation layer in the API — the account’s own permissions remain the control.

​
Writes are ordinary writes

Because those writes go through the same server-side logic as the equivalent Hermès screen, they produce the same result: the same activity entries, the same notifications to the OVRSEA team, the same tasks closed. If you reconcile against the activity feed, a change made by asking appears there exactly as one made by clicking.

​
For the people using it

This page covers what a developer needs to know. For what Ask Zach can do day to day, with examples, see AI at OVRSEA.