The Kater API
The API reference now shows only the Kater API: the 24 routes that Kater promises to your code and your agents. Each route is stable or beta. A stable route changes only by adding. A beta route can change, after an entry here 30 days before. Each change to the API from now on is listed here.
New
- Six groups, one for each job: who you are, find what the data team built, read the numbers, what a metric means, keep definitions in step, and what people asked.
- Each field shows its default and its limits, such as the most rows a page holds.
- A list that grows, such as the kinds of objects a conversation made, says so. Treat a value that you do not know as a kind that you cannot show yet.
Changed before release
POST /v1/dashboard/openonly reads by default. Setscaffoldto true to save Kater’s starting dashboard when a workspace has none.POST /v1/catalog/explainnames the file that defines a field by its path from the content root, not by a link to a folder on the server.POST /v1/sync/statusgives each sync astate:synced,never_syncedorunreadable, and the time inat.POST /v1/catalogwithsearchanswers typed hits, and withshowtyped tags.- No answer names a folder on Kater’s server:
rootis gone fromPOST /v1/catalog,POST /v1/compile,POST /v1/runandGET /v1/logs/query.









