Nicia Brains

The system of record for what your company knows.

Not what it bills or ships — that stays in your database, your CRM, your ledger. What it knows: the decisions, the standards, the current answer. A Brain is that boundary, scoped to a customer, a project, a team, or an operation. Documents, typed records, and the evidence behind every claim, in one place with one set of keys and one review queue.

Your people and the agents you already run both read from it and both change it. Nothing lands until someone approves, and Nicia tells you where every sentence came from.

Agents don’t need memory. They need a Brain.

One Brain · chain of custodyIllustrative lifecycle

01Sources

Records

Documents

Agent writes

02Review

ProposedHuman or policy decisionAccept · edit · reject

03Context

Accepted stateCited answer[1] source passage

04Receipt

Verifiedrcp_019fWhat the read consumed

curl https://api.nicia.ai/v1/brains/tenant:acme/context \
  -H "authorization: Bearer $NICIA_KEY" \
  -H "content-type: application/json" \
  -d '{ "prompt": "What should I know before this renewal call?" }'

{
  "data": {
    "text": "Renewal closed 2026-03-14. Acme renewed at $120k for 24 months.",
    "citations": [
      {
        "source": "hubspot:deal:412",
        "slug": "brain-evidence-0dd3e2449851d9ba41924c42bd7a61375a8b78050bfe2ca7192eb918d626236a",
        "quote": "Renewal closed 2026-03-14. Acme renewed at $120k for 24 months."
      }
    ],
    "staged": 0,
    "warnings": [],
    "receipt": "rcp_019ffefe",
    "truncated": false
  }
}

Run one Brain for yourself or one per customer across a fleet of millions. It is the same handful of calls either way, and you address every one of them by your own handle — no Nicia ids to store.

Two ways in

Build context into your product →

You are shipping an AI product and every customer needs their own context. Create a Brain per customer, write documents or records, request context, and scale the fleet — without building retrieval infrastructure you did not want to own.

Three calls, about five minutes.

Share your team’s knowledge →

Your team’s knowledge is a folder of markdown on somebody’s laptop, a wiki export, or a pile of pages in Notion and Drive. Bring it somewhere everyone — and everyone’s agents — reads the same copy, and connect Claude Code, Codex, or anything else that speaks MCP.

One command, about two minutes.

Both paths are the same Brain and the same API. Start wherever you are.

Nothing to connect

Nicia is not a connector layer between your existing tools. Notion, Docs, Drive and Confluence are editing surfaces built for people, and they are good at that: their unit is a page, their API is designed around a person clicking, and nothing in them carries a typed field, a review step, or a record of why something changed. A document is a fine rendering and a bad database.

So an import reads, and never writes back. Nothing in your existing tools is modified, no sync is established, and no credential of ours touches your systems. What you get is a copy, which makes this cheap to try and cheap to abandon.

A copy does drift once people keep authoring somewhere else, so treat it as a trial with a shelf life rather than a resting state: run both for a week or two, compare the answers, and then decide whether the Brain becomes the place you write. That cutover is your call and your moment.

Knowledge keeps being born in Slack, email, and meetings, and your agents can keep bringing it in. Capture is many to one. Authority is one place.

Put knowledge in

Both on-ramps work on a brand-new Brain with no schema step.

• Documents — text, markdown, PDFs, transcripts, and whatever metadata you already have. Nicia chunks, indexes, and extracts.
• Records — typed structured data. Send what is now true and Nicia works out what changed.

Get context out

• Context — one prompt in, grounded text and citations out. This is the endpoint most integrations only ever need.
• Search and queries — full-text and semantic search, and exact predicates over typed fields when you need them.

Shape it

• Schemas — start with none, keep the default, pick the neutral vocabulary, adopt a pack, or declare your own. You can change your mind later.

Trust it

• Review — agents propose, you accept. Trusted pipelines write directly.
• Receipts — every read records exactly what it was shown, so you can defend an answer months later.

Run it at scale

• One Brain per customer — provisioning as a pure function of your tenant id.
• Handing out keys — scoped keys for an app, a department, or an end user.

Work as a team

• Bring your knowledge — a folder, a Drive, or a repo, imported and searchable in one command.
• Share it — invite people, connect Claude Code and Codex to the same copy.
• Keep it good — review, agent-assisted maintenance, and export whenever you want.

Already running agents on Nicia?

The agent platform — agents, runs, conversations, streaming, and webhooks — is documented under Using the platform.