Kontour for developers

Kontour CLI

@kontourai/cli

npm install --global @kontourai/cli

The kontour command. It works out which Kontour packages you already have installed and hands your command to the right one. It never reaches for the registry, downloads a missing package, or changes a version behind you — so the same command does the same thing offline.

Datum

@kontourai/datum

Your model registry. Define providers, models, and roles once, then resolve which backend, which model, whose key, what URL. It doesn't call models for you — apart from four opt-in commands that reach a provider: a probe, a connection test, model discovery, and a catalog refresh.

Bearing

@kontourai/bearing

Which model is actually good at what, and where that judgement came from. Compiles observations into immutable, digest-stamped catalog snapshots, and ranks models for a given runtime — without calling any of them.

Relay

@kontourai/relay

One way to call a model whether it sits behind a vendor SDK, a local engine, a hosted service, or a command-line harness, so changing providers doesn't mean rewriting the call. Each adapter has to declare what it can't do — streaming, tool calls, token counts — rather than quietly approximating it.

Dispatch

@kontourai/dispatch

Chooses which model handles a job from rules you write — required capabilities, a token and cost budget, retries, fallbacks — and hands back a record of which one ran, why it was picked, and what it actually spent. Budgets can be held across concurrent calls and across restarts.

Conduit

@kontourai/conduit

Installs an agent's skills, hooks, commands, and context files into whichever coding tool someone is running, through one adapter instead of one per host. It probes each host for what it genuinely supports, and the install receipt lists every asset installed with its SHA-256 digest — no file contents, no target paths, no credentials.

Traverse

@kontourai/traverse

Pulls structured fields out of documents against a schema you supply, and hands back proposals for a person to review — each one still carrying the passage it came from.

Forage

@kontourai/forage

Fetches untrusted URLs safely and keeps a snapshot of what came back, so a crawl can be replayed instead of re-guessed. Refuses requests aimed at your internal network.

Lookout

@kontourai/lookout

Watches sources you re-check over time and tells you what changed since the last look. Built on Forage's snapshots; it doesn't extract fields itself.

Plumb

@kontourai/plumb

Runs your deployment's own health check on a schedule, and when it fails, hands the failure to an AI agent working in a separate clean clone that opens a pull request or an issue. Its instructions forbid touching the live checkout or production data — prompt-level guardrails today, not a sandbox.

Ephemeris

@kontourai/ephemeris

Turns time into a trigger. Watches the freshness deadlines on Kontour trust bundles and nudges Flow to re-evaluate when one expires, and works out when a recurring schedule — cron, a fixed interval, or a one-shot — should next fire in a given timezone, daylight-saving included. It never decides anything itself; it only taps something else on the shoulder.

Kontour UI

@kontourai/ui

The interface pieces our own screens are built from: buttons, panels, badges, dialogs, form controls, and the CSS variables behind them, for React or plain custom elements. Useful if you are building an operator screen that should match ours; skip it if you already have a design system you like.