Command Structure
At a Glance
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.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
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.Logs
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

