> ## Documentation Index
> Fetch the complete documentation index at: https://apidoc.ovrsea.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ask Zach

> The OVRSEA assistant, built into Hermès

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 today.

It matters here because it is the third way an agent touches your account — and the one your
colleagues are most likely to be using while you build against the API.

## What it is

A single conversation, in the Hermès header. There is no separate console and no set of buttons to
learn: you type the question the way you would ask a person, in your own language, and Zach answers
against your account's real data.

It reads anything you can already see, and it can perform the
[agent actions](/ai/agent-actions) on your behalf.

## Confirming a change

Zach never changes anything as a side effect of answering. When a request implies a write, it first
states what it is about to do — which shipment, the current value, the new value — and waits.

For actions with a confirmation card, review the proposed change and click the confirmation
button to send your decision to Zach.

The remaining actions have no card; there Zach states the change and waits for a yes in the
conversation.

Both are designed so a person sees the change first, and in practice that is how it behaves. Be
aware of what it is, though: this is a confirmation step in the assistant, not a second
authorisation layer in the API. It is not a substitute for the permissions on the account, and it
is not a control you should rely on to stop a write that the account is allowed to make.

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 your OVRSEA team, the
same tasks closed. A change made by asking is not a second-class change.

## How it relates to the API

Ask Zach is not a different permission model. It resolves what you can see and change from your own
Hermès account, exactly as the REST API resolves it from a token and the MCP server from an OAuth
sign-in.

Use it when the person needing the answer is already in Hermès. Reach for the
[MCP server](/ai/mcp-server) when they would rather stay in their own assistant, and the
[REST API](/introduction) when it is your code asking rather than a person.