Product guide

The built-in API cards

The key-authenticated API and MCP cards — one to push documents in, one to ask questions — set up from the console.

This category covers the four ways your own software reaches Naxis Assistant directly: the Ingestion API for pushing documents in, the Messaging API for asking questions over HTTP, Recall for a program's one-call question with a choice of which sources to look in, and MCP for plugging the assistant into Claude, Cursor and other AI tools. Pick the one that matches what you're building — a pipeline that feeds it content, an app that needs grounded answers, an agent that asks and keeps its own notes, or an AI tool that should be able to do all of it.

All four run on the same foundation: a single Bearer key per source or channel, the same access-control rules as the console (an ingested document's groups, a channel's guest groups, or a person's own access), and the same audit trail as every other surface. MCP doesn't add a new capability — it's a third protocol in front of the same two keys, plus an admin key that can also run the console itself.

Start with whichever direction you need: see Ingestion API to push documents in, Messaging API to ask questions from your own application, Recall to ask in one call choosing where to look, or MCP to connect an AI tool. Each key is scoped to exactly one of ingest or ask — a key minted for one plane cannot be used for the other, except an admin key, which reaches both plus the console.

In this section

Was this page helpful?

Was this page helpful? Sign in with Google Sign in to tell us — or leave a comment.

Last updated 20 Sep 2026