CLI

@dcision/cli installs the dcision command. Use it to call deployed decisions from a terminal or a script, and to keep decision schemas in version control with offline validation.

InstallCopy Anchor Link

# In a checkout of the Dcision repository — Node.js 22 and pnpm 10
pnpm install
pnpm --filter "@dcision/cli..." build   # builds @dcision/core, then the CLI

npm install -g ./packages/cli           # puts `dcision` on your PATH, linked to this checkout
dcision --version

The ... after the package name builds the packages the CLI depends on first. Without installing it globally, run node packages/cli/dist/bin.js instead of dcision. It needs Node.js 20 or newer.

Quick startCopy Anchor Link

# Save an API key (prompted, so it stays out of your shell history)
dcision login

# Run a deployed decision
dcision decide lead-qualification \
  --state '{"message":"We need pricing for 500 users and want to start next month.","company_size":500}'

# Print the raw API response, with the full distributions
dcision decide lead-qualification --state-file lead.json --probabilities --json

CommandsCopy Anchor Link

loginCopy Anchor Link

dcision login                                  # prompts for the key
dcision login --api-key "$DCISION_API_KEY"     # non-interactive
echo "$DCISION_API_KEY" | dcision login        # reads stdin when piped
dcision login --api-url https://api.dcision.io # also saves the API URL

The key is stored in ~/.config/dcision/config.json with file mode 600 (readable only by you). dcision logout removes it. Prefer --api-key from an environment variable or stdin over typing a key in a command line that ends up in your shell history.

configCopy Anchor Link

dcision config set output json
dcision config get api-url
dcision config list

decideCopy Anchor Link

dcision decide <slug> [--state <json> | --state-file <path> | --stdin] [--probabilities] [--idempotency-key <key>] [--json]

Pass the state with one of --state, --state-file or --stdin.

The CLI reads a state as JSON when it is a JSON object, array or string, so it calls and checks decisions with an object, a list or a text state: --state '["Hi!", "Can I get a quote for 50 seats?"]'. Anything else — plain text, a number — is sent as text; a value that starts with { but doesn't parse is sent as text too, with a warning.

decide is safe to retry: it generates an Idempotency-Key when you don't pass one and retries once on network errors with the same key, so a lost response is replayed rather than run — and billed — twice.

The human-readable output shows the decision and version, the action and its reason, one row per question with its result and confidence, the distributions with --probabilities, and the latency, model, estimated cost and execution ID. Use --json for weighted levels, composites and the destinations of the response.

# Pipe states from another tool
jq -c '.lead' event.json | dcision decide lead-qualification --stdin --json

# Text decision
dcision decide spam-detection --state '"Congratulations! You won a gift card, click here."'

# Your own idempotency key, e.g. the record ID
dcision decide support-routing --state-file ticket.json --idempotency-key ticket-55120

templates and initCopy Anchor Link

dcision templates                                       # lists the nine templates: id, name, description
dcision init                                            # writes ./decision.json
dcision init lead.json --template lead-qualification    # starts from a template
dcision init triage.json --template ticket-triage       # a pattern template: speculative fan-out
dcision init lead.json --template lead-qualification --force   # overwrites an existing file

The template ids are lead-qualification, support-routing, spam-detection, agent-routing, rag-relevance, ticket-triage, voice-banking, resume-screening and customer-service-router — see Templates.

init writes a decision schema — the same JSON the app's editor shows under Decision schema. Without --force, it doesn't overwrite an existing file.

validate and check-stateCopy Anchor Link

dcision validate decision.json
dcision check-state decision.json --state '{"message":"Hi, can I get a demo?"}'
dcision check-state decision.json --state-file samples/lead-1.json

Both run offline, with the same rules as the app and the API: validate reports every schema issue with its path — questions, structured entries, composites, policies and their and conditions, destinations — and summarizes a valid schema: its state, questions, number of policies and destinations. check-state reports why a state would be rejected with 422 INVALID_STATE — object, text and list states alike. Use them in CI to keep schemas and sample payloads in sync with your code. The engine's token budget, which also counts the questions, is checked by the API when the decision runs.

Environment variablesCopy Anchor Link

Exit codesCopy Anchor Link

if ! dcision validate decision.json; then
  echo "decision.json is invalid" >&2
  exit 1
fi