Developer API / Overview

The engine, as a procedure.

A small HTTP surface over a deterministic relational substrate. Observe text, ask a question, emit a traversal, derive an edge. No sampling. No model call. No external knowledge.

The surface

The HTTP surface is deliberately smaller than the Python engine. Operator routes for account and security administration are not part of the developer contract.

What a session looks like

1. 01

   Observe

   Admit text as a node. The response is its 16-character invariant hash.

2. 02

   Relate

   Use /observe-seq to admit an ordered sequence. The sequence writes directed transitions; a single node has nowhere to traverse.

3. 03

   Query or emit

   /query anchors on a hash or admits unknown text first. /emit only reads an existing anchor. An absent anchor is a seam, not a new node.

4. 04

   Derive

   Reconstruct a justification between two nodes. Promotion is earned through the gate; the HTTP route reports whether it happened.

What it is not

This is not a chat-completion endpoint, a vector store, or an embedding database. It does not consult external knowledge. It derives from relations that have been admitted into the instance.

Instance model

The server is intentionally single-threaded: calls are serialized so ordering is deterministic. There is no HTTP route to clear nodes or reset the substrate. Treat every observation as durable.

Start here