Anakin Insights
anakin-ops 0.2.0 is a zero-dependency Node 18+ CLI (npm install -g anakin-ops) that operates the Anakin platform end to end: agent CRUD with streaming chat, pages publishing, counterpart messaging over lanes, ERP ledger reads, database introspection, and file builds. Reads and approved operations run on scoped API keys; destructive and credential-lifecycle operations stay browser-gated with explicit scope errors instead of cryptic failures.
A single zero-dependency binary (anakin, also installed as anakin-ops and ops) that covers the daily operator loop: anakin dashboard opens a live interactive cockpit (move with arrow keys, / to filter the fleet, Enter for agent detail, r to refresh, space to pause); anakin agent list|get|chat|create|update|delete runs the full agent lifecycle with optional SSE token streaming; anakin pages list|create|update drives the owner publishing surface; anakin lanes send messages counterparts over lanes (chat, email, and lane channels); anakin ledger ping|stock|invoices reads ERP state; anakin files upload|compile|export-pdf moves the workspace vault; anakin limits reports plan caps and rate limits. Everything renders as human tables on a TTY and single-line JSON with --json for pipelines.
Developer keys (ak_live_*) carry scopes such as agents:read, data:read, keys:manage, and webhooks:manage. The platform resolves the key, checks the route against an explicit allowlist, and enforces the mapped scope — reads and approved data-plane operations pass; anything else fails closed with a 403 that names the missing scope or states that a browser session is required. The CLI surfaces that message verbatim instead of printing raw auth internals, and anakin login never persists a key the gateway rejects (offline saves require explicit --force). Multi-profile credentials live in ~/.anakin/credentials.json with restricted permissions, overridable per call via --api-key, --profile, or environment.
Start with anakin smoke for contract, auth, and fleet health, then anakin dashboard to watch the fleet. Triage counterparts with anakin lanes list and reply with anakin lanes send. Check money with anakin ledger ping and anakin billing usage, quotas with anakin limits, storage with anakin files usage. Publish with anakin pages create and anakin files upload. Automate all of it: every command is scriptable with --json, --once (cockpit), and --timeout, and anakin run chains discovery, inspection, and sandboxed compute into one autonomous loop.
Lane revocation, API key rotation and deletion, file and page deletion, ledger postings and payments, secret and binding management, and approval decisions require an interactive browser session. These are irreversible, money-moving, or credential-lifecycle operations where a deliberate human gesture is the control — not friction. The CLI refuses them closed for API keys and tells you exactly that, so automation never silently half-executes a destructive plan.
Behavior verified against the live gateway on 2026-10-15 with scoped ak_live_* keys across reads, benign writes, and destructive refusals, plus the CLI suite (20 tests) and the worker allowlist suite. Scope maps and command coverage follow the 0.2.x CLI and the deployed worker allowlist; re-check anakin limits and the docs reference before scripting quotas or money-adjacent flows.
Run npm install -g anakin-ops (Node.js 18 or later, zero dependencies), then anakin login --key ak_live_... to verify live against the gateway. Credentials persist per-profile with restricted permissions; anakin whoami confirms identity and anakin doctor reports environment, contract, and key source.
Agents, pages, lanes, ledger reads, database connectors, files, limits, sandbox runs, and smoke probes all run from the terminal on scoped API keys. Lane revocation, key rotation, deletes, ledger writes, and invoices require a browser session by design — the CLI fails those closed with an explicit scope message instead of a cryptic auth error.
Run anakin mcp to expose the platform as a Model Context Protocol stdio server (search, agent list and chat, lanes, files, database, raw execution) with validated arguments and spec-conformant error shapes. Point any MCP-capable assistant at the anakin binary and it operates with the same scopes as the key it is given.
They were removed in 0.2.0 to keep one pure Anakin surface: external contract tooling and edge-database bridges no longer ship in the binary. The API contract search (anakin search), the platform docs, and the committed SDK client cover those workflows now.