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:

Facts

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

Deploy

Analytics — Dry Run

Analytics — Impact Simulation

Analytics — Dataset

Profile

Filters: --version <vid> (default: live), --from / --to (ISO-8601 instants), --cache HIT|MISS. Percentiles are withheld () below 100 samples; judgment is relative only — see the Performance Profiling guide.

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.

Integrations

Logs

Webhook Subscriptions

Platform event webhooks receive deployment lifecycle notifications (VERSION_PUBLISHED, DEPLOYED, ROLLED_BACK, UNDEPLOYED, DEPLOY_SCHEDULED, DEPLOY_SCHEDULE_CANCELED). Separate from rule-level EMIT_WEBHOOK actions. 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.