Notes API
Collaborative documents that become searchable organisational knowledge the moment they are saved.
Chordian Notes is a document workspace whose notes are written into Chordian Memory. A note you save is chunked, embedded, entity-extracted into the knowledge graph, and synthesised — so what your team writes becomes searchable organisational knowledge by default, not by a separate export step.
Two planes, and why the split matters
The API is split across two surfaces. The split is a data-residency guarantee, not an implementation detail.
| Plane | Serves | Runs on |
|---|---|---|
| Metadata — this API | note tree, projects, onboarding, search | Chordian platform |
| Content — Memory API | Markdown bodies, versions, assets | the memory that owns the note |
Note bodies never transit the Chordian platform. On a sovereign deployment they are written directly to your own infrastructure, and the platform sees only identifiers, titles, timestamps and sync state. That property is what makes Notes usable by customers who cannot let document content leave their environment.
Where a note lives
Notes inherit the memory model rather than inventing one.
| Memory type | Markdown files | Metadata | Vectors & graph |
|---|---|---|---|
| Shared secure memory | Chordian-managed storage, tenant-isolated | Chordian platform | shared stores |
| Dedicated memory | your box | Chordian platform | your box |
| Sovereign (your infrastructure) | your box — never leaves | your box | your box |
Air-gapped deployments run Notes fully offline.
Storage format
A note is Markdown with YAML frontmatter:
---
page_id: pg_7f3a91c2
project_id: prj_a1b2c3d4
title: Q3 Architecture Decisions
version: 7
format: md
---
# Q3 Architecture Decisions
Body content in standard Markdown…It is readable and editable with no Chordian tooling — no proprietary wrapper, no base64 blob. Exporting a project yields a zip that preserves the note tree as nested folders. This is a product guarantee: your documents remain yours, in a format that outlives any vendor.
Next
- Getting started — authenticate and make your first call
- Reference — every endpoint