DocsOverview

Company Brain

Company Brain is an organization's permission-scoped knowledge graph. It holds what a company knows about itself, and the AI clients your team already uses can read it under the same access rules a person has. Nothing outside AiAx writes to it: new knowledge arrives as a proposal a person approves.

What it is

Most company knowledge is scattered across documents, tools and people's heads. Company Brain models it as a graph, so an agent can answer how the business actually works and cite the exact pieces of knowledge behind the answer.

Nodes: What the organization is made of: people, departments, projects, processes, systems, agents, strategies, data sources and policies. Every node has an id, a title, a summary and an access level.
Relations: The verbs between nodes: who manages what, which process depends on which system, which policy governs which project. Relations are what turn a list of documents into knowledge.
Access: Every node carries an access level. A reader sees only the nodes their tier allows, and a relation is visible only when both of its ends are.
Evidence: Knowledge a person has confirmed carries a verification date and a review window. Inferred knowledge is marked as a hypothesis and never presented as fact.

Node types	Relations
organization, person, department, project, agent	is part of, belongs to, manages, works on, owns, uses, depends on
SOP / process, tool, strategy, data source, policy	governs, can access, supports, champions, targets, needs clarification with

Everything new is a proposal

An external client can read the graph and propose to it. It cannot write. A proposal lands in the approval inbox in the AiAx portal, where a manager sees the exact stored content and decides. Only an approval changes what the organization knows.

This is the whole trust model in one sentence: a wrong answer from a model becomes a rejected proposal, never a corrupted knowledge base.

Read tools are annotated as read-only and change nothing.
Proposal tools need an explicit scope on top of the token, and say so plainly when they lack it.
The approval binds to the stored proposal, not to what the client says it sent.
Every tool call is recorded against the token that made it.

Connect a client in one minute

Open Connect AiAx in the portal and create an access token. AiAx shows it once. It is bound to your organization, carries a viewer tier and can be revoked at any time.
Put the token in your shell or your client's secure storage. The configuration below only references it, so the token never lands in a file you might share.
Add the server to your client with the command for it.
Ask the client to read the onboarding status. When it answers, the connection works.

Store the token (placeholder shown)

export BRAIN_MCP_TOKEN=brain_xxxxxxxxxxxxxxxxxxxxxxxx

The endpoint is https://aiaxagents.ai/api/mcp. Authentication is a bearer token in the Authorization header.

Per client

Claude Code

claude mcp add-json --scope user aiax '{"type":"http","url":"https://aiaxagents.ai/api/mcp","headers":{"Authorization":"Bearer ${BRAIN_MCP_TOKEN}"}}'

Run it in a terminal that already has the token in its environment. The command stores a reference (${BRAIN_MCP_TOKEN}), not the secret.

Cursor: add to .cursor/mcp.json

{
  "mcpServers": {
    "aiax": {
      "url": "https://aiaxagents.ai/api/mcp",
      "headers": { "Authorization": "Bearer ${env:BRAIN_MCP_TOKEN}" }
    }
  }
}

Keep the token in Cursor's secure storage rather than in the file itself.

OpenClaw: Connects through AiAx CLI. We do not offer manual header configuration, because OpenClaw has no documented secure token reference yet.
Claude: Coming with OAuth. The direct connection is not ready, so we publish no command for it.
ChatGPT: Coming with OAuth. The direct connection is not ready, so we publish no command for it.
Obsidian: The first version of the plugin is built: read-only, with graph, search and sources. Distribution is pending community catalog review.

A good first prompt

Agents work best when you state the boundary up front. This prompt orients a client and keeps it honest about the approval step.

Paste into your client

Connect to AiAx and help me with onboarding. Run get_onboarding_status first. Tell me what is complete, and ask only about the next missing area. Run get_onboarding_action_catalog before you propose a change, and follow its schema. Use query_index and read_concept when Company Brain has relevant knowledge. Do not guess. Show me exactly what you send with propose_onboarding_action. Do not submit anything until I confirm. Every proposal must be approved in AiAx.

Where to go next

MCP reference: the eight tools, their inputs and the machine contract an agent can parse.
Security and governance: tokens, tiers, scopes, approvals, freshness and erasure.
Knowledge sources: which systems can feed the brain and what disconnecting does.
CLI: the command line tool for signing in and connecting a client.
The whole documentation set as one plain text page lives at https://aiaxagents.ai/llms-full.txt. Paste it into any model that needs the full picture.

CLI