# Overview

Source: https://docs.settlemint.com/docs/developers/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. Use it for local setup, scripted operations, 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. Each use case below maps to a guide that covers the relevant commands and patterns:

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

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

The CLI groups its operations by domain. Auth and config 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 session management, API keys, organization context, and local preferences.
* `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 onboarding, identity management, 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 and evidence collection.
* `xvp-settlements` for cross-value protocol settlement operations.

## Operating model [#operating-model]

CLI operations follow the same DALP permission model as the API. Most require an authenticated session and run against the active organization. When you script anything that changes state, use explicit input values, JSON output, error handling, and a list-before-create pattern where duplicate creation would be unsafe.

You control the local CLI environment: platform URL, active organization, credentials, output format, scripts, and CI secrets. DALP enforces your permissions and org context when each request reaches the platform.

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

## Next steps [#next-steps]

<Cards>
  <Card title="Getting started" href="/docs/developers/cli/getting-started">
    Install the CLI, authenticate with device flow login, and run your first commands. Start here if you have not yet set up a local session.
  </Card>

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

  <Card title="Scripting and automation" href="/docs/developers/cli/scripting">
    Use JSON output, shell safeguards, and CI patterns for repeatable operations. Covers credential handling, error exits, and pipeline setup.
  </Card>

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