Skip to main content
The Sentrial CLI ships with @sentrial/sdk as the sentrial binary. It is designed for humans and agents: local setup, scriptable inspection, and CI checks all use API-key auth instead of browser login.

Install

From the root of an agent repo:
The installer bootstraps the CLI through npm, installs the right SDK package for the project, and writes safe example files without committing a real API key.

Authentication

Agents should use API keys from organization settings:
For local human use, you can save the key once:
The CLI resolves credentials in this order:
  1. --api-key
  2. SENTRIAL_API_KEY
  3. ~/.sentrial/config.json
Use --api-url or SENTRIAL_API_URL for self-hosted or local API targets.

Setup Commands

Generated examples use placeholder API keys, so they are safe to commit as references.

Sessions

Events

Signals And Diagnosis

CI Gates

Use evaluate in scripts to fail a build when an experiment regresses:
For agent automation, prefer JSON:

Reserved Commands

These commands are intentionally present but guarded until the backing APIs are public: