Skip to content
NiciaDocs
Beta. This surface may change before GA; breaking changes are dated in the changelog.

Bring your knowledge

If your team’s knowledge is a folder of markdown — a wiki export, an Obsidian vault, a docs repo, a pile of meeting notes in Drive — this is the shortest path to something the whole team can query and connect their agents to.

It does not have to be a folder. If your knowledge lives in Notion, Drive, Confluence, or Slack, the agent you already run has access to those, and that makes it the connector: hand it curl -sL nicia.ai/import.md and it will read those sources and populate the Brain the same way.

Either way this reads, and never writes back. Nothing in your existing tools is modified or moved, no sync is set up, and no credential of ours touches your systems. You get a copy, so trying costs you nothing. A copy drifts once people keep authoring somewhere else, so run both for a week or two, compare the answers, and then decide whether the Brain becomes the place you write.

Drag the folder in

Section titled “Drag the folder in”

Open app.nicia.ai, create a Brain, and drop a folder or a .zip on it.

Scanning team-wiki.zip
  312 markdown files, 4.1 MB
  detected: 41 people, 12 projects, 260 notes


Creating Brain team:acme
Uploading  ████████████████████  312/312
Indexing   ████████████████████  done


Brain ready: https://app.nicia.ai/brains/team:acme

That is the whole thing, and nothing you already built is lost on the way in:

What you have What it becomes
Folder structure Topics
Frontmatter keys Preserved as document metadata
[[wikilinks]] Relations between subjects
A type: you invented A kind, if you promote it — kept either way
Anything else Prose, searchable and citable

If you curated this by hand, had an LLM organise it, or brought it from GBrain, that work carries over as structure rather than being flattened back into a pile of text. Keys we do not recognise are stored, not dropped — they become queryable the moment you declare them, retroactively. See Schemas.

Re-run the same import any time. It is keyed on each file’s path, so a second pass updates what changed and leaves the rest alone.

Import from your terminal

Section titled “Import from your terminal”
Terminal window
npx nicia import ./team-wiki --brain team:acme

A CLI form of the same importer, for scripting an import instead of dragging a folder — same rules, same result.

What you get

Section titled “What you get”

A document per file, searchable immediately. Nicia also reads them for records — the people, projects, and decisions it can recognise — each one anchored to the passage it came from.

Ask the Brain something in app.nicia.ai, or from a connected agent once you’ve shared it with your team — “who owns billing?” comes back grounded in the actual pages, with a citation for every claim:

Billing is owned by the Payments squad; Priya Raman has been the DRI since the March reorg.

— handbook/teams/payments.md, notes/2026-03-11-reorg.md

If an answer looks wrong, the file it came from is one click away.

What if my markdown is messy?

Section titled “What if my markdown is messy?”

That is the normal case and it is fine. Import never fails on structure it does not recognise — untyped files become plain documents, which are still fully searchable and citable. Structure is something you add later if you want it, not a precondition.

If you want to see what Nicia thinks your shape is, GET /v1/brains/{handle}/schema/candidates reports the field patterns it noticed across your files (person — 41 files — fields: name (98%), team (71%), and so on); POST /v1/brains/{handle}/schema/promote turns one into a declared kind with filterable fields. Promoting a kind costs nothing to skip.

Next

Section titled “Next”