Skip to main content

Command Structure

At a Glance

Each section below covers the commands in detail.

Auth

Status

lexq status verifies that the API is reachable and your key is valid by calling the whoami endpoint and reporting latency. lexq auth whoami returns the full authentication details. Use status for quick health checks; use whoami for identity verification.

Groups

Versions

Rules

Example:
paymentAmount is the action’s targetVar, so it must already be a registered fact (lexq facts create). Otherwise the command fails with ACT-032.

Facts

lexq facts action-metadata is read-only and cached per session — safe to call anytime when designing rules.

Domain Templates

apply creates a policy group with curated fact definitions and sample rules. Use --name to override the generated group name, and --force to skip the confirmation prompt. Run preview first — it shows exactly what will be created without changing anything. See Domain Templates for what each template contains.

Deploy

rollback also takes --expected-current-version-id and --expected-current-deployment-id. Pass the currentVersionId and currentDeploymentId that lexq groups get returned, and the rollback is rejected if the group changed after you read it. See Rollback.

Analytics — Dry Run

Analytics — Impact Simulation

Analytics — Dataset

Profile

Filters: --version-id <vid> (default: live), --from / --to (ISO-8601 instants), --cache HIT|MISS. Calls that name a version (Specific Version Execution, Dry Run, Impact Simulation, Decision Replay) are never included. A percentile shows – until there are enough samples; higher percentiles such as p99 need more. A rule is flagged slow by comparing its p50 with the median p50 of the rules in the same group, version, phase, and cache state, so there is no fixed millisecond cutoff. The Performance Profiling guide gives the minimum sample count for each percentile and how the comparison works.

History

Replay

Provenance

There is no reveal command — revealing PII plaintext is console-only by design, and every console reveal writes an audit row first.

Logs

Resolving or ignoring a failure log is console-only: an organization admin does it under Management → Failure Logs. API keys, which the CLI uses, can read failure logs but cannot change their status.

Webhook Subscriptions

Platform event webhooks receive deployment lifecycle notifications (VERSION_PUBLISHED, DEPLOYED, ROLLED_BACK, UNDEPLOYED, DEPLOY_SCHEDULED, DEPLOY_SCHEDULE_CANCELED). They operate at the platform level: rules themselves do not emit webhooks. Example:

Serve

→ MCP Server Setup Guide

Standard Workflow

Cannot create rules without a DRAFT version. Cannot publish without rules. Cannot deploy a DRAFT. Always dry-run before publishing.