CLI

$ ivf — the Axiom command line

Policy authoring, schema inspection, validator monitoring, operation submission, and audit queries — all from the terminal. Scriptable, pipeable, CI-ready.

Node.js 18+ESMnpm

Installation

Get started

npm

# Install globally — makes the ivf command available in your terminal
npm install -g @xenta/ivf-cli

# Or as a project dependency
npm install @xenta/ivf-cli

verify installation

ivf --version
ivf --help

configuration

# Recommended — save your API key once
ivf config set api-key axm_live_...
ivf config get

# Or use environment variables
export AXIOM_API_KEY=axm_live_...
export AXIOM_GATE_URL=https://gate.axiom.xenta.pro   # default, can be omitted

# Optional — AI assistant (for ivf policy assist)
export OPENAI_API_KEY=your_openai_key
export GEMINI_API_KEY=your_gemini_key

Command reference

Six command groups.

Configure the CLI — set your API key, Gate URL, and platform URL. Stored in ~/.axiom/config.json. Override any value with an environment variable.

ivf config set api-key<key>

Save your Axiom API key locally. Keys are stored in ~/.axiom/config.json and never logged.

ivf config set gate-url<url>

Override the Gate URL. Defaults to https://gate.axiom.xenta.pro. Useful for local development.

ivf config set platform-url<url>

Override the platform API URL. Defaults to https://axiom-api.xenta.pro.

ivf config get

Show current configuration — API key (redacted), Gate URL, platform URL, and config file path.

AI policy assistant

Plain language in. Deployable policy out.

ivf policy assist translates plain-language intent into a validated policy artifact and human-readable Policy Contract. Deterministic validation always runs last — no AI in the enforcement path.

example session

$ ivf policy assist

> Describe what you want to protect:
  "Treasury transfers over $10,000 require two approvers
   and must be blocked on weekends"

> Axiom AI: Understood. Mapping to transaction.v1 schema,
  HIGH tier, dual-control requirement, time-bound constraints.

  Summary of Intent:
  — Schema: transaction.v1
  — Tier: HIGH (100 validators)
  — Skillsets: auth-intent, policy-compliance, transaction
  — Allow threshold: 67/100
  — Dual control: required
  — Time bounds: weekdays only

  Risk assessment: MEDIUM — single-jurisdiction time constraint.

> Confirm, refine, or cancel? [C/R/X]: C

> Compiling final artifact...
> Validation: VALID (0 errors, 1 warning)

> Enter a name for this policy (optional):
  Treasury Transfer Policy

> Type DEPLOY to deploy, or anything else to cancel: DEPLOY

✅ Policy deployed successfully.
   Policy ID: pol_da581c49c58d44c0a5c4f1bd

Workflow examples

Where it fits in your stack.

Policy authoring in CI

Validate policy artifacts as part of your CI pipeline before they ever reach a deployment gate.

shell

# In your CI pipeline
ivf policy validate ./policies/treasury-transfer.json

# Exit code 0 → valid, deploy proceeds
# Exit code 1 → validation failed, CI blocks

Gated deployment

Submit a deployment operation for quorum verification before your deploy script runs.

shell

# Request verification (LOW tier — 7 validators, 5 must agree)
ivf exec request AUTHORIZATION \
  --payload '{"requesterId":"ci-bot","resource":"prod-cluster","action":"deploy"}' \
  --committee-size 7 \
  --allow-threshold 5 \
  --deny-threshold 3

# Check status and receipt
ivf exec status <operationId>
ivf exec receipt <operationId>

Audit query

Pull a time-windowed audit report from the ledger for compliance review.

shell

# Query last 24 hours
ivf audit query --since 24

# Trace a specific operation
ivf audit trace 71af2690-5f37-459f-a922-546a9454cf46

Governance belongs in the terminal.

Get API Key Read the Docs