The vault screen, the AI client you already use, and your team’s API reach the same engine and the same vault. Only the door changes.
Three doors, one conversation
Screen, AI client, or your own system
On screen, you ask next to the documents and click the source to land on the slide. In your AI client, the vault is one more thing it can query. Through the API, your team automates what a person does by talking.
In all three, the answer comes with its address, and the agent is built to refuse when it is not in your documents.
The agent channel is an open standard
Public standards for sign-in and discovery
The channel an AI client uses is a resource server in the web’s standard authorization design, so an integration does not have to learn a convention of ours first.
One substrate, several readers
A new channel does not invent a new surface
An open API and an agent channel let your team build a third-party agent, a panel or a workflow on the same substrate. The agent’s operations are a subset of the API’s, by contract, so the doors never become different products. The set is in capabilities.
The door changes; the owner of the vault does not
The conversation stays with you, wherever you speak from
From any door: the same isolation between organizations, the same metering, the same record of who did what. Nothing the agent answers is built from another company’s data. The text sent to the model follows the provider’s retention terms. This page and the privacy page say so; in the vault, the agent’s first line does too. More in privacy.
Why the model never touches the file: the conversation is with the AI.