Documentation

For when you are already inside and have run into something specific. Each page says what can be done, what it is called on the screen, and what will happen — and, just as plainly, what is not there.

• Connecting a toolYour workspace address, the token a tool signs in with, and what each refusal means.
• Tracker APIWhich requests of the widely used tracker’s REST API Kaiku answers, and where it behaves differently.
• Search (JQL)The part of the tracker’s query language Kaiku understands — and, as plainly, the part it does not.
• Wiki APIThe wiki speaks the REST API of the widely used corporate wiki: what it answers, what it stores, and its query language.
• MCP serversKaiku’s own MCP server, and the open-source one written for the widely used tracker and wiki — both work against your workspace.
• AgentsCall one in a comment and it answers in the thread — on your access, reading only that project, and never deciding anything itself.
• Releases and automatic movesVersions, environments, and rules that move an issue when a merge request is opened, a pipeline deploys or a release ships.
• Legal referencesAn act named in an issue or a wiki page becomes a reference: marked in the text, listed under it, and read from its official publisher.
• The requirements registerA ready-made project: a register of what a company is obliged to do — the norm, the obligation, who answers for it, what proves it. What it brings, how to take it, and how to make it yours.
• Open source projectsA project bound to a public repository, opened for anybody to read by a link: what a visitor sees and never sees, how outsiders take part, search engines, and why its people take no seat.
• Taking your data outExporting a project in one archive, downloading what we hold about you, and having an account or a workspace erased.
• Billing and read-onlyThe trial, what happens when a paid period ends, and how long a workspace is kept after that.

Something missing, or not as described here? Write to hello@kaiku.tech