Documentation.
Kaitoi turns models, code, services and domain tools into programmable building blocks you can compose, run and ship. These pages cover the ideas that make the rest make sense, and the REST API you build against.
Concepts
What to understand before you build anything on Kaitoi.
- Projects A project is the saved unit of work in Kaitoi. It holds a graph, carries a version for safe concurrent edits, and is the thing the REST API reads and writes.
- Graphs and nodes A graph is nodes plus connections. A node is one typed unit of work with input and output pins. Everything Kaitoi runs is a graph, including the things that do not look like one.
- Runs A run executes a graph, from a saved project or from an inline graph you send with the request. Runs are asynchronous, observable while they happen, and report what they cost.
Kaitoi Studio
The app itself: how work is shaped, run and read on the canvas.
Kaitoi Core
The programmable platform and REST API beneath Kaitoi Studio.
Kaitoi CLI
Kaitoi on your own machine: local recipes, connected services, and Kaitoi Code.
- Install the CLI Kaitoi CLI is the local companion app. Install it to run recipes on your own machine, connect local services to Kaitoi Studio, or use Kaitoi Code from the terminal.
- Kaitoi Code Penny in your terminal. Code works with local files in a folder you trust, Kaitoi projects and graphs, runtime recipes, and approved local commands, and can hand long coding tasks to the Crew.
- Recipes and the local runtime A recipe is the reproducible local execution contract for a model or piece of code. Turn a GitHub repository or a Hugging Face model into one, run it on your own machine, and drive it from a node in Kaitoi Studio.
- Configuration and troubleshooting Code's optional config file, and the five things that usually go wrong: a missing command, a lost login, a stopped runtime, a recipe Kaitoi Studio cannot see, and a failed download.
API reference
Every endpoint, generated from the running API rather than maintained by hand, so it cannot drift from what the server actually accepts.