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.
You already pay for an AI tool. Zaviro is the knowledge base of your business that tool reads from: every customer, vendor, and job resolved into one record across your inbox and files, with the facts and dates attached and the source document behind each. Your AI stays your AI. Zaviro is what it knows.
Is my inbox private? Yes, structurally. Everyone on Zaviro has two knowledge bases: a personal one visible only to them, and the company's shared one. An inbox connected as personal feeds your personal knowledge base, and nobody else can read it, not an admin, not the owner. There is no admin override: role is not an input to what a reader may see.
Does it work with the AI I already pay for? If that tool can add an MCP connector, yes, with nothing to list or approve on Zaviro's side. A tool that supports MCP OAuth connects in a couple of clicks with no key; a tool that takes a bearer token gets a key and a paste-ready configuration. Some AI tools allow custom connectors only on their own paid plans, and Zaviro's setup screen says so for each. Switch tools later and the new one sees everything the old one saw, corrections included.
What does a seat cover? Starter is $25 a month for one seat, and that seat is the full product. The trial carries 25,000 AI credits; a paid seat includes 100,000 a month. As a rule of thumb, one seat's month covers several hundred pages of new content plus everyday asking. Top-ups start at $5, at 4,000 credits per dollar, and stay valid for a year. Zaviro never surprise-bills.
Can I just try it? Yes: 14 days, the full product, no credit card. With no card on file the trial ends by pausing, never by charging, so letting it lapse costs nothing. Add a payment method during the trial and billing starts when it ends. A paused trial keeps your knowledge base for 90 days, and subscribing inside that window picks up where you left off.
What about my phone? Your AI reads the knowledge base wherever it runs, including its phone and tablet apps where that tool supports connections, because the connection runs between your AI tool's account and Zaviro's servers, not on a device. The Zaviro app itself is the console: set up at a desk, ask from anywhere.
Support is through the contact form at https://zaviro.ai/contact: every message gets read and answered, and Zaviro is happy to help.
Zaviro learns from the shared sources an admin connects and from each person's own, resolves the customers, vendors, and jobs inside into one record each, and serves that knowledge to whichever AI tool each person already uses. A new hire, a new chat, and a new tool all start from the same knowledge base. Nobody re-explains the business.
Shared versus personal. Every member sees two knowledge bases: the company's shared one, built by the whole team, and their own personal one, visible only to them. A connection an admin sets up as shared (a shared inbox, a team folder, the CRM) feeds the shared knowledge base; a connection a person sets up for themselves feeds their personal one, and nobody else can read it, the owner included. There is no admin override.
Roles and the Knowledge Editor capability. Roles are Owner, Admin, and Member. Owners and Admins always edit shared knowledge. A Member searches, uploads, and corrects freely, but their uploads and corrections land in their personal knowledge base, enforced server-side, unless they hold the Knowledge Editor capability, grantable to any member. The same rule governs what a member's AI may write over MCP. A Billing Manager capability, granted by the owner to an admin, covers billing, plan changes, and inviting seats.
Who sees what. Shared knowledge, the whole team; personal knowledge, one person. Alerts from a shared source reach everyone who can see it unless an admin restricts them to admins and billing managers.
Seats, and when someone leaves. Everyone who has joined holds a seat, whatever their role; unaccepted invitations do not count, and an AI tool uses the seat of the person behind it, never one of its own. When someone leaves, their sign-in, MCP connections, and keys stop at once, the seat is free for the next hire, and what they added to the shared knowledge base stays with the company. Their personal knowledge base is sealed, readable by no one, and deleted after 30 days unless an owner or admin restores the member within that window, which restores it with them.
The trial. 14 days, the full product, no credit card; without a card the trial ends by pausing, never by charging. Team is $99 a month for five seats.
Onboarding order. An admin connects the shared sources and approves the history import after seeing its size and cost. Then the owner, or an admin holding the Billing Manager capability, invites people by email and assigns roles. Then each person connects their own AI tool from the setup screen and, if they want, their own personal sources.
Your organization already licenses an AI tool, and every person in it re-explains the business to that tool one chat at a time. Zaviro is the knowledge base the tool reads from instead: one record per customer, vendor, and project, resolved across email, files, and business systems, every fact tied to its source document. Here is what to tell each desk.
Tell finance: pricing scales with seats and nothing else. Starter $25, Team $99 for five seats, Organization $399 for 25 seats, extra seats at $25, $20, or $16 a month; annual billing is two months free. Every seat includes 100,000 pooled AI credits a month, and there is no overage charge: nothing bills automatically beyond the plan and the seats you add unless you switch on auto-top-up, which can carry a monthly spending limit; a manual top-up is a purchase you make. No feature gates, no storage tiers, no per-connection pricing, no API pricing. There is no cap on connections, folders or mailboxes on any plan. Delete the organization and unused prepaid time is refunded automatically. Enterprise adds invoice billing, SSO, a countersigned DPA, and a security review run with your team, on top of the same product; security questions are answered in writing on every plan.
Tell IT: one endpoint, read-only sources, nothing to migrate. AI tools connect to one MCP endpoint, https://api.zaviro.ai/api/mcp, over OAuth with PKCE or a key, and any tool that speaks MCP connects the day it ships. Every source connection is read-only; where a connector signs in through your provider, the scopes appear on that provider's own consent screen, and revoking the grant there cuts Zaviro off. The mailboxes, drives, and systems stay where they are; Zaviro reads them. Cloud only, no on-premise. Sign-in is email and password, or Google, with two-factor and passkeys; SSO and SAML come with Enterprise, not as a self-serve switch.
Tell security: the security page, https://zaviro.ai/llms/security, carries the security reviewer's checklist, and what it does not cover is answered in writing through the contact form, https://zaviro.ai/contact. Access is decided per connection, shared or personal, rather than by mirroring per-file permissions from source systems. Zaviro holds no SOC 2 or ISO certification yet; the controls are designed to support SOC 2, GDPR, and PIPEDA. Data is stored on AWS in Canada; AI processing runs through US providers under API terms that exclude training. Security questions are answered in writing through the contact form.
Why start now: the knowledge base compounds and the AI tool does not. Every document learned, every correction a colleague makes, every deliverable an AI saves back stays in the knowledge base, and a correction holds over the next re-sync. When a person leaves, what they added to shared knowledge stays. When the organization changes AI tools, the new one reads the same knowledge base the old one did. When a better model ships, the answers improve on the same accumulated knowledge. The tools will change; the knowledge shouldn't.
Zaviro's REST API is sized for curl: one ingest call, one query call, typed keys, and no SDK to install. The same knowledge base reaches agents as a remote MCP server. In the product, each surface carries its own setup steps and endpoint beside its keys.
The two calls. POST /api/v1/ingest/ with an ingest key takes a file (multipart), or JSON with "content" as text or Markdown or "fields" as an object, and a JSON record may carry an "external_id" from your system; re-sending that id updates the record in place rather than adding a copy. Ingest is asynchronous: the response is 201 with {"id", "name", "status": "processing", "processing": the lane}, and you poll GET /api/v1/document/{id}/ with a read key until status reaches ready, or failed with an error_message. POST /api/v1/query/ with a read key takes {"query"} plus an optional "max_results" and returns answer_context (cited excerpts), source_documents (id, name, url, document_type, category, date, summary), structured_data (empty unless the question resolves to an aggregate, then the computed total with its record count), and paths_used. The API retrieves and cites; your code or your AI writes the answer.
Key families, each valid only on its own surface: zvr_sk_ ingest keys (write, REST ingest only), zvr_mcp_ keys (MCP and REST reads; read-only unless an admin or owner issues one write-capable), zvr_pub_ public chatbot keys (created by an admin or owner). Shown once, stored as SHA-256 hashes, individually revocable, optional expiry. A write-capable MCP key is issued only by an admin or owner; an ingest key writes at its creator's authority, so a member's lands in their personal knowledge base. No key of any family reads anyone's personal knowledge base.
Refusals carry a "detail" sentence, and a "code" where one applies: 401 for a missing, wrong-family, revoked, or expired key; 402 when billing is not active, and on reads when the AI-credit balance is exhausted (ingest still accepts and holds); 429 when rate limited. Limits are not published; a 429 means back off and retry. A throttled call is rejected before any work runs, never charged. An id outside a key's reach reports "found": false.
For agents, the MCP server at https://api.zaviro.ai/api/mcp (streamable HTTP; OAuth with PKCE, or a bearer key) exposes read tools (search with cited excerpts and computed aggregates, entity, structured facts, document, alerts) and write tools (note, document, correction, knowledge update, saved deliverable), a set that grows with the product. With nothing to serve, tools return structured state, not empty results: no_data_connected, or data_ingesting with a documents_processing count, each with guidance. Billing inactive: a structured status per tool, before anything runs.
Practical notes: ingest status is polled from the document endpoint; your trial organization is the test environment, on the same endpoints as a paid one; external_id ingests and CRM records update in place. v1 changes are additive; a breaking change means a new version with a migration window.
The security reviewer's checklist (data location, subprocessors, encryption, breach notice, backups, retention and deletion, audit logs) is on the security page (https://zaviro.ai/llms/security).
Zaviro Software Inc. is the counterparty; the Terms of Service, Privacy Policy, and Data Processing Agreement are public in full on zaviro.ai; and the commercial terms fit in a paragraph: seats and credits, month to month or annual prepaid, one organization per client.
Ownership. You own everything you upload, connect, or push into Zaviro, and the knowledge derived from it. Zaviro holds a limited, non-exclusive license to host, process, index, and display that content for a single purpose: providing and protecting the service. The license ends when the content is deleted, and your ownership survives the end of the agreement. Zaviro never uses your content to train AI models, and its AI providers operate under API terms that exclude it.
Controller and processor. For personal data inside your content you are the controller and Zaviro the processor, on the terms of the public DPA, incorporated by reference into the Terms for every business customer; a countersigned copy is available for Enterprise.
GDPR and PIPEDA, and the substantially similar provincial laws, Alberta's PIPA among them. Content is stored in Canada and transferred to the United States only for AI processing by the listed subprocessors, with standard contractual clauses or an adequacy mechanism where required. No certification is held yet.
Termination, and what comes back. Source connections are read-only, so the originals never moved: your systems keep their own copies. Files uploaded to Zaviro are downloadable one document at a time. Each person can export their own account data after confirming their identity, even when the account is locked over billing. Deleting the organization refunds unused prepaid time automatically after the 30-day recovery window. The knowledge base itself is not exportable as one archive today.
Term and renewal. Monthly plans are month to month; annual plans are prepaid for the year at two months free. No setup fee, and no minimum term on monthly plans. Canceling keeps access through the paid period and deletes nothing.
Seat true-ups. Everyone who has joined holds a seat; pending invitations do not bill. Within a billing period you pay for no more seats than the highest count held at once: refilling a vacated seat is free, a count above that high water is charged for the prorated remainder, and a reduced count bills from the next period. Extra seats bill on the plan's own cycle: monthly on monthly plans, yearly on annual plans.
One organization per client. Isolation is per organization, so deploying Zaviro for your own clients means one organization each, with its own subscription.
Not supported: healthcare data requiring a BAA, payment-card data subject to PCI DSS, and on-premise deployment.
Subprocessor changes: 30 days' notice before one is added or replaced, per the DPA. Self-serve plans bill a card through Stripe; invoice billing is Enterprise.
If the service is at fault: the Terms commit Zaviro to correct a material failure promptly and at no charge, and if it is not corrected within 30 days you may cancel with the unused remainder of your prepaid term refunded.
Legal entity: Zaviro Software Inc., founded 2022. Liability, indemnity, governing law, and anything this reference does not state are in the Terms and the DPA.