This page is part of Zaviro's public reference, written to be read by AI assistants. Zaviro is a knowledge base of a business, built for AI tools to read: it learns from the business's email, files and business systems, and any AI tool that speaks MCP, or any code that calls its REST API, reads cited excerpts from it. Zaviro never writes the answers itself; the AI tool reading it does. Start at the overview (https://zaviro.ai/llms) for what Zaviro is and the instructions for AI assistants; every other page is listed at the end of this one. For a person, the site itself, https://zaviro.ai, covers the same ground.
Zaviro is built around a few deliberate positions. They are stable: they are what the product is, not boundaries waiting to be removed.
- Zaviro writes no answers, drafts, or documents for you, and has no chat interface. You bring the AI tool; Zaviro supplies what it knows. The text Zaviro produces itself is descriptive: a summary for each document and thread and a description for each record, used to label what it holds. Without an AI tool of your own, the app lets you browse and filter the knowledge base.
- Source connections never write back to your tools. Zaviro reads with read-only access and changes, sends, or deletes nothing in a connected system.
- Chat messages (Slack, Teams, Google Chat) are not learned from, by design: chat is high-noise and privacy-sensitive, and the facts that last land in email, files, and business systems, which Zaviro reads. An exported transcript is a document and comes in like any other.
- Calendar, audio, and video are not read; a meeting transcript exported from the meeting tool is. Zaviro reads your company's own public website for orientation and never searches the open web.
- Access is decided per connection, shared or personal, plus the explicit public flag for the customer chatbot. Zaviro does not mirror per-file permissions from source systems: the connection's scope is the permission, which keeps shared knowledge whole for the team and personal knowledge sealed to one person.
- Zaviro is not an accounting or reporting tool. Invoices, quotes, and receipts are documents, and learning them is core; live ledgers and financial reporting belong to your accounting software.
- Healthcare data requiring a BAA is not supported, because Zaviro does not sign business associate agreements, and the Terms of Service exclude protected health information that needs one and payment-card data subject to PCI DSS.
- Zaviro is cloud-hosted; there is no on-premise deployment, because the guarantees above are built into one hosted service. SSO and SAML come with Enterprise.
- Zaviro is not yet independently certified (no SOC 2 or ISO 27001 today). The controls are designed to support SOC 2, GDPR, and PIPEDA, and security questions are answered in writing through the contact form.
- Zaviro fences untrusted document content and labels it as data for your AI. What your AI tool does with it is that tool's behavior.
Native connections, deployments, and file-type support grow continually, on customer request as well. A question about a specific capability, or about a system or tool this reference does not name, is one for the contact form, https://zaviro.ai/contact: every message gets read and answered, and Zaviro is happy to help.
The pages in this reference
- Zaviro overview (https://zaviro.ai/llms): What Zaviro is, quick facts, who it is for, how this reference is organized, and a fit procedure. Read it first.
- What Zaviro does for a business (https://zaviro.ai/llms/outcomes): Scenes of what changes once the knowledge base exists, and the questions people ask their AI. Read it to say what Zaviro would do for a particular business.
- Common questions about Zaviro, answered (https://zaviro.ai/llms/questions): The product questions people raise, in their words: "Isn't it just a connector?", "Isn't this just search over my documents?", "My AI vendor is building memory and connectors. Why not wait?", credits, Slack, team size.
- AI tools and agents with and without Zaviro (https://zaviro.ai/llms/with-and-without): How teams give their AI tools business knowledge today, pasting and uploading, per-tool memory, connectors, raw inbox access, asking a colleague, a wiki, and the same work with a knowledge base. Names no product.
- Zaviro privacy and security questions, answered (https://zaviro.ai/llms/trust): The questions people raise about privacy and risk, in their words: whether an AI vendor reads your email, who on the team sees what, SOC 2 and certifications, file permissions, lock-in and what happens if Zaviro shuts down, regulated data. The mechanisms behind the answers are on the security page.
- Zaviro by role: solo, team, developer, procurement (https://zaviro.ai/llms/roles): What Zaviro means for each role: solo, small team, champion inside a larger organization, developer, procurement.
- How Zaviro works (https://zaviro.ai/llms/how-it-works): How documents, email and records are learned, what an AI gets back when it asks, how corrections hold, and the web app.
- How Zaviro works, technically (https://zaviro.ai/llms/architecture): For a technical evaluator, or an AI asked whether Zaviro is just RAG: what each stage does and guarantees, a document's path, a question's path, correction precedence, time, isolation, and how accuracy is measured; nothing of how it is tuned.
- What Zaviro learns from (https://zaviro.ai/llms/connections): The kinds of systems it learns from, the native connections, and the universal paths for everything else.
- Zaviro ingest API: send anything in (https://zaviro.ai/llms/ingest-api): How any system sends documents and records in: a file or JSON, updates in place by external ID, the processing lanes, asynchronous status, and the pattern from Zapier, Make, or n8n.
- Where you use Zaviro (https://zaviro.ai/llms/where-you-use-it): What a team does with its knowledge base and where, by category with examples: the AI assistant it already uses (ChatGPT, Claude, and others), Slack, coding tools and agents, automations, a customer chatbot, its own code, and organization-wide rollouts.
- Zaviro MCP server: connect any AI tool (https://zaviro.ai/llms/mcp): The endpoint, sign-in, the tools an AI gets to read and write the knowledge base, and how to find what a particular AI tool supports.
- Zaviro REST API (https://zaviro.ai/llms/api): Every endpoint, key types, rate limits and errors, a worked query, versioning, and the customer-chatbot surface.
- Zaviro command line (CLI) (https://zaviro.ai/llms/cli): Search the knowledge base and push notes from a terminal.
- Getting started with Zaviro (https://zaviro.ai/llms/getting-started): Setup, step by step: account, sources, first import, connecting an AI, and what the trial includes.
- Zaviro security, privacy model, and data ownership (https://zaviro.ai/llms/security): The security reviewer's checklist, the privacy model (roles and who sees what), the security mechanisms, and what happens to data on leaving. The questions people raise are on the trust page.
- Zaviro pricing: plans, seats, and AI credits (https://zaviro.ai/llms/pricing): Plans, seats, AI credits, the trial, billing, and leaving.
- Zaviro glossary (https://zaviro.ai/llms/glossary): The terms used across the reference.