Naxis Assistant
Documentation
Grounded answers from your organisation’s own documents — every answer cites the exact passage it came from, and anything that isn’t in your material is refused rather than guessed. Here’s how to install it, run it, and build on it.
curl $NAXIS/v1/messages \
-H "Authorization: Bearer $KEY" \
-d '{"text":"Does the client renew?"}'
{
"text": "Renews 1 Sep 2026 [1].",
"abstained": false,
"citations": [{ "n": 1 }]
}Start here
From nothing to an assistant your whole team uses — five steps, in order.
-
One command on a Linux server you control — or nothing at all, hosted by Naxis. You’ll have been told which applies to you, with a link to match.
-
113 connectors bring in your files, wikis, mailboxes, team chat, meetings, databases and business systems — each with one read-only credential, set up in minutes.
-
Invite your team, group them, and allow each source to the groups that may read it. Access is allow-only from the first minute — nobody sees a document they weren’t given.
-
Put the assistant where your people already talk — Teams, Slack, WhatsApp, a widget on your site — beside the web chat it always has.
-
A short page of what they’ll see and how to ask — share it on day one.
The product guide
The complete administrator’s manual — the same help that lives inside the console, mirrored here, section by section.
- How it works6 articlesWhat the assistant is, how it turns your documents into cited answers, and why those answers can be trusted.
- Sources113 connectorsConnectors bring your organisation’s knowledge into the assistant — files and drives, mailboxes and chat, databases and business systems. Each takes one read-only credential; pick a category to set it up connector by connector.
- Chat channels16 channelsPut the assistant where your team already talks — Teams, Slack, WhatsApp, the website widget and more.
- People & access4 articlesAccounts, invitations, groups, and the allow-only access model that decides who sees what.
- Settings, operations & compliance11 articlesSettings, branding, email, background jobs, the audit trail, and the security & privacy facts.
- The built-in API cards4 articlesThe key-authenticated API and MCP cards — one to push documents in, one to ask questions — set up from the console.
- For your team6 articlesWhat the people who use the assistant see — share this with your team.
What it does
- Grounded answers. The assistant reads your connected documents and answers only from them. Every claim carries a citation you can open to see the original passage.
- Refuses rather than guesses. If the answer isn’t in your material, it says so — it never invents one.
- Respects access. People only ever see answers drawn from documents they’re allowed to read. Permissions mirror your sources.
- Meets people where they work. A web chat, plus messaging channels (Telegram, WhatsApp, Slack, Viber) and an embeddable widget.
- Runs itself. It indexes new material on a schedule, keeps itself healthy, and installs its own updates in a window you control.
The two ways to run it
| On your server (self-hosted) | Hosted by Naxis (managed) | |
|---|---|---|
| Where it runs | A Linux server you control | The Naxis platform |
| Your data | Never leaves your server | Held by Naxis under agreement |
| To set up | Run one command | Open a link |
| Maintenance | Automatic updates & backups | Handled for you |
Hosted by Naxis is what every plan comes with. Running it on your own server is arranged with Naxis directly rather than chosen at signup — ask us and we set it up with you. Either way you’ll have been told which one applies to you, and been sent a link to match: follow Install — on your server or Install — hosted by Naxis.
Building on top
The HTTP API lets you push documents into the knowledge base and ask questions from your own code, authenticated by a key you create in the console. Stuck? See Troubleshooting and the FAQ.
Last updated 9 Sep 2026