# Overview

Source: https://docs.settlemint.com/docs/developer-guides/cli/overview
Choose the right DALP CLI guide for installation, command lookup, scripting, CI automation, and AI agent workflows.



The DALP CLI is the command-line control plane for the Digital Asset Lifecycle Platform. Operators and developers use it for local administration, repeatable scripts, CI jobs, and AI agent workflows that call DALP through typed commands.

<Mermaid
  chart="`
flowchart TD
User[&#x22;Operator, developer, or automation job&#x22;] --> Auth[&#x22;Authenticate and choose an organization&#x22;]
Auth --> Inspect[&#x22;Inspect platform state&#x22;]
Auth --> Configure[&#x22;Configure users, settings, compliance, and assets&#x22;]
Auth --> Automate[&#x22;Run scripts, CI jobs, or agent workflows&#x22;]
Inspect --> Evidence[&#x22;JSON, Markdown, YAML, or human-readable output&#x22;]
Configure --> Permissions[&#x22;DALP permissions and active organization context&#x22;]
Automate --> Repeatable[&#x22;Repeatable command sequences&#x22;]
`"
/>

## When to use the CLI [#when-to-use-the-cli]

Use the CLI when the work starts in a terminal or automation environment:

| Task                  | Use the CLI for                                                                                                     | Start with                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| First access          | Install the package, log in, verify your session, and set output preferences.                                       | [Getting started](/docs/developer-guides/cli/getting-started)     |
| Command lookup        | Find the command group for tokens, users, compliance, monitoring, settings, XvP settlement, and other DALP domains. | [Command reference](/docs/developer-guides/cli/command-reference) |
| Repeatable operations | Build scripts that read JSON, handle errors, and run the same operational sequence safely.                          | [Scripting and automation](/docs/developer-guides/cli/scripting)  |
| AI-assisted work      | Expose DALP commands to coding agents through shell execution, MCP, generated skills, and structured output.        | [AI agent integration](/docs/developer-guides/cli/ai-agents)      |

## How the CLI is organised [#how-the-cli-is-organised]

The CLI groups commands by operating domain. Authentication and configuration commands prepare the local session. Domain commands then work against the active DALP instance and organization.

Common command families include:

* `auth`, `login`, `logout`, `whoami`, and `config` for sessions, API keys, organizations, and local configuration.
* `tokens`, `token-sales`, `external-tokens`, and `fixed-yield-schedules` for asset lifecycle and token-related operations.
* `users`, `identities`, `identity-recoveries`, `kyc`, `contacts`, and `compliance-providers` for participant, identity, and compliance workflows.
* `settings`, `asset-type-templates`, `compliance-templates`, and `system` for platform configuration and administration.
* `account`, `actions`, `blockchain-transactions`, `monitoring`, and `search-results` for inspection, evidence, and operational follow-up.
* `xvp-settlements` for cross-value protocol settlement operations.

## Operating model [#operating-model]

CLI commands follow the same DALP permission model as the API. Most commands require an authenticated session and run against the active organization. Commands that change state should be scripted with explicit input values, JSON output, error handling, and a list-before-create pattern where duplicate creation would be unsafe.

The operator or automation owner controls the local CLI environment: platform URL, active organization, credentials, output format, scripts, and CI secrets. DALP enforces the authenticated user's permissions and organization context when each command reaches the platform.

The CLI is not the runtime interface for application traffic. Use the DALP API for service integrations that need a stable programmatic interface, request lifecycle control, and application-owned error handling. Many production teams use both: the API for application logic, and the CLI for setup, checks, scripts, and incident follow-up.

## Next steps [#next-steps]

<Cards>
  <Card title="Getting started" href="/docs/developer-guides/cli/getting-started">
    Install the CLI, authenticate with device flow login, and run your first commands.
  </Card>

  <Card title="Command reference" href="/docs/developer-guides/cli/command-reference">
    Find the command group and examples for each DALP operating domain.
  </Card>

  <Card title="Scripting and automation" href="/docs/developer-guides/cli/scripting">
    Use JSON output, shell safeguards, and CI patterns for repeatable operations.
  </Card>

  <Card title="AI agent integration" href="/docs/developer-guides/cli/ai-agents">
    Connect DALP CLI commands to AI agents through shell execution, MCP, and generated skills.
  </Card>
</Cards>