append_nodes
ChatGPTAppend content to nodes, optionally setting metadata or kind. Repeating a call can append duplicate content. Accepts 1 to 100 same-kind operations in one database, executed in input order and atomically; any failure rolls back the whole batch. The complete request must fit 256 KiB. Changes to a public database or published node can become publicly visible.
context
ChatGPTAnswer a normal question from task-scoped page bodies, links, and source evidence. Start here when the question does not identify exact pages. For known paths use path reads directly. For inventories or exhaustive investigations use list/search and fetch candidate bodies. Do not answer from search hits alone; report insufficient or truncated evidence.
create_folders
ChatGPTCreate folders. An existing folder is left unchanged; an existing non-folder is an error. Parents must exist or precede children in the batch. Accepts 1 to 100 same-kind operations in one database, executed in input order and atomically; any failure rolls back the whole batch. The complete request must fit 256 KiB. Changes to a public database or published node can become publicly visible.
delete_nodes
ChatGPTDelete only explicitly selected nodes using current expected_etag. Folder deletion may also require expected_folder_index_etag. Accepts 1 to 100 same-kind operations in one database, executed in input order and atomically; any failure rolls back the whole batch. The complete request must fit 256 KiB. Changes to a public database or published node can become publicly visible.
edit_nodes
ChatGPTReplace exact text using the current expected_etag. By default old_text must match exactly once; multiple matches fail. Set replace_all=true only when every occurrence should change. Include unique surrounding text to target one occurrence. Accepts 1 to 100 same-kind operations in one database, executed in input order and atomically; any failure rolls back the whole batch. The complete request must fit 256 KiB. Changes to a public database or published node can become publicly visible.
fetch_many
ChatGPTRead 1 to 10 exact page references: search result ids OR public Kinic Wiki page URLs supplied by the user or another tool. References may belong to different databases; send them together in one call. Known references need no preceding search, context, or path conversion. Never pass ChatGPT citation tokens such as turn0file0. If only database_id and path are known, use path reads. Returns page bodies, etags, and item-level errors.
find_databases
ChatGPTUse this when you need to discover which Kinic Wiki database visible to the current caller matches a user task.
get_profile
ChatGPTReturn the stable profile ID and a short PID label represented by this request's authenticated credentials for connection management.
list
ChatGPTList nodes under a prefix without reading content. limit accepts 1-99; default 99. A truncated result is not a complete inventory. Use prefix / for root inventory and prefix discovery, /Knowledge for curated notes, and /Sources for raw evidence inventory.
memory_manifest
ChatGPTDiscover Store API roots, capabilities, roles, and limits for one Kinic Wiki database visible to the current caller.
move_nodes
ChatGPTMove or rename nodes using source expected_etag. Set overwrite only when explicitly requested; an existing destination also requires expected_target_etag. Accepts 1 to 100 same-kind operations in one database, executed in input order and atomically; any failure rolls back the whole batch. The complete request must fit 256 KiB. Changes to a public database or published node can become publicly visible.
multi_edit_nodes
ChatGPTApply several exact-text replacements in one node with one current expected_etag. Edits run in order on the preceding result; EACH edit replaces ALL matching occurrences. Include unique surrounding text when only one occurrence should change. A missing match fails the entire batch. Accepts 1 to 100 same-kind operations in one database, executed in input order and atomically; any failure rolls back the whole batch. The complete request must fit 256 KiB. Changes to a public database or published node can become publicly visible.
mutate_nodes_batch
ChatGPTUse when different operation kinds must execute in one transaction. Apply 1 to 100 ordered operations atomically in one database; any failure rolls back the whole batch. Operations and dedicated tools: write (write_nodes), append (append_nodes), edit (edit_nodes), multi_edit (multi_edit_nodes), mkdir (create_folders), move (move_nodes), delete (delete_nodes). Prefer the dedicated tool for same-kind operations; never split a mixed atomic batch into separate calls. Changes to a public database or published node can become publicly visible.
read_paths
ChatGPTRead 1 to 10 exact known paths in one database, with current etags and item-level errors. No preceding search or context call is needed. Preserve successful items when another path fails. For search ids or URLs use fetch_many.
search
ChatGPTFind candidate pages for a topic or broad investigation in one database. limit accepts 1-20; default 10. Use prefix / to include all roots, /Knowledge for notes, or /Sources for source documents. For broad coverage vary queries and inspect list when needed. Fetch selected result bodies with fetch_many before answering; previews are not complete evidence. For an ordinary question use context; for known paths use path reads.
write_nodes
ChatGPTPreferred for every create/full-replacement request, including one node. Create or replace 1 to 100 nodes in order and atomically in one database; any failure rolls back the whole batch. Changes to a public database or published node can become publicly visible.
