Chitmonk docs

Chitmonk is a meeting companion for rooms with people in them. A laptop on the table listens through its own microphone, transcribes on the device, lets the room say who is speaking, and ends with a receipt. There is no account and no server. A meeting stays in the browser it was recorded in until someone exports it.

These pages are what you need to work with it, and no more.

For people

• Using Chitmonk: the keys, the languages, where meetings are kept, and what to know before you rely on it.
• Privacy: what stays on the device, and the two things that can ever leave it.
• Terms of use: what you may do, who owns what, and what Chitmonk is and is not responsible for.
• Chet: the chipmunk. Not needed. Recommended.

For developers and agents

• The .chit bundle: the file a meeting leaves the app in. A ZIP with a manifest and one event log per meeting.
• The event log: every event, its fields, and the rules for replaying a log into a meeting.
• Read a bundle and write one: short scripts, standard library only.
• Other exports: the Markdown, plain text and Word files, for when a reader is all you need.
• For agents: where the plain-text copies of these pages are, and the rules for touching someone's meetings.

Two files to keep next to you: the JSON Schema of everything in a bundle, and a small sample bundle.

What is not here

Chitmonk is proprietary for now. There is no source code here and no API to call: the app has no server, so there is nothing to call. Integration is the file. If you can read and write a .chit, you can get meetings out of Chitmonk and into it. More on that.