# AI assistants

Source: https://docs.settlemint.com/docs/user-guides/ai-agents/overview
Connect AI assistants to DALP through the CLI and MCP so operators can inspect platform state and run controlled asset operations with the same permissions as their account.



AI assistants use the DALP CLI as the controlled product surface for natural-language work. The assistant can inspect tokens, users, identities, compliance configuration, and operational state through CLI commands or MCP tools. State-changing operations still run with the authenticated user's permissions and the active organisation context.

<Callout type="info" title="For developers">
  If you are integrating coding agents into build, test, or scripting workflows, use the [CLI AI agent integration
  guide](/docs/developer-guides/cli/ai-agents). This page is for operators deciding how AI assistants fit into platform
  work.
</Callout>

## What the assistant can control [#what-the-assistant-can-control]

The assistant is not a separate DALP role. It uses the CLI session you give it, so the same permission checks, organisation scope, and API validation apply.

| Work area                | Typical assistant task                                                                        | Control that still applies                                                             |
| ------------------------ | --------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Token operations         | List assets, inspect supply, prepare mint or pause commands, and explain current token state. | The account must have the token permissions required by the underlying operation.      |
| Identity and KYC         | Find users without verified identity, inspect KYC status, and help prepare follow-up work.    | KYC, identity, and trusted-issuer rules remain platform controls.                      |
| Compliance configuration | Compare token compliance modules and prepare configuration commands.                          | Compliance changes require the same roles and approvals as manual CLI or dapp work.    |
| Reporting                | Summarise token, holder, and operational data from structured CLI output.                     | The assistant only sees data exposed to the authenticated user.                        |
| Troubleshooting          | Check authentication, organisation context, command output, and platform errors.              | The assistant cannot bypass missing roles, expired sessions, or API validation errors. |

<Mermaid
  chart="flowchart TD
    operator[Operator] --> assistant[AI assistant]
    assistant --> cli[DALP CLI]
    cli --> mcp[MCP tools]
    cli --> api[DALP API]
    api --> controls[Permissions, organisation scope, validation]
    controls --> platform[Tokens, identities, compliance, and reporting]
    platform --> audit[Platform audit and operational records]"
/>

## Choose the right integration mode [#choose-the-right-integration-mode]

| Mode               | Use it when                                                                            | Setup path                                                  |
| ------------------ | -------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| CLI shell commands | The assistant can run terminal commands and parse JSON output.                         | Install the CLI, authenticate, and set JSON output.         |
| MCP tools          | The assistant supports MCP and should call typed DALP tools instead of shell commands. | Register the DALP CLI as an MCP server with `dalp mcp add`. |
| CLI skills         | The assistant discovers Markdown skill files and uses them as command guidance.        | Install generated skills with `dalp skills add`.            |

The CLI exposes the same operational surface in each mode. MCP avoids shell parsing by presenting commands as typed tools. Skills give agents command-specific instructions and examples.

## Set up an operator workstation [#set-up-an-operator-workstation]

### 1. Install and authenticate the CLI [#1-install-and-authenticate-the-cli]

```bash
npm install -g @settlemint/dalp-cli
dalp login --url https://your-platform.example.com
```

Confirm the session before giving the assistant access:

```bash
dalp whoami --format json
```

### 2. Pin the organisation context [#2-pin-the-organisation-context]

Operations are scoped to the active organisation. Switch organisation before starting an assistant session when the workstation has access to more than one organisation.

```bash
dalp auth org-list --format json
dalp auth org-switch <organizationId> --format json
```

### 3. Use JSON output for shell-based agents [#3-use-json-output-for-shell-based-agents]

```bash
dalp config set format json
```

Structured output gives the assistant stable fields to parse instead of terminal tables.

### 4. Register MCP and skills when your assistant supports them [#4-register-mcp-and-skills-when-your-assistant-supports-them]

```bash
dalp mcp add
dalp skills add
```

`dalp mcp add` registers the CLI as an MCP server for supported local agents. `dalp skills add` installs command guidance that agents can discover before they run DALP commands.

## Operating rules for AI-assisted work [#operating-rules-for-ai-assisted-work]

Use AI assistants for preparation, inspection, and repeatable command execution. Keep approval and accountability with the operator.

* Ask the assistant to query state before it proposes a mutation.
* Review the exact command, target token, amount, recipient, and organisation before any state change.
* Keep high-risk operations under the same approval process used for dapp or CLI work.
* Use roles to limit what the authenticated account can do. Do not rely on prompt wording as a permission boundary.
* Keep production credentials in the local credential store. Do not paste tokens, private keys, recovery codes, or customer data into the assistant conversation.
* Capture operational evidence from DALP records and transaction output, not from the assistant's summary alone.

## Example operator prompts [#example-operator-prompts]

Use prompts that force the assistant to inspect before acting.

```text
List all equity tokens in the active organisation. Do not make changes. Return the token name, symbol, address, total supply, and paused status.
```

```text
Check which users do not have verified identity. Group them by current status and propose the next manual action for each group. Do not approve or issue claims.
```

```text
Inspect this token's compliance configuration. Tell me which controls are active, which roles can update them, and what command you would run if I approve the change.
```

## Troubleshooting [#troubleshooting]

### DALP tools are not available [#dalp-tools-are-not-available]

1. Check that the CLI is installed.

   ```bash
   dalp --version
   ```

2. Check authentication.

   ```bash
   dalp whoami --format json
   ```

3. Re-run MCP registration if your assistant supports MCP.

   ```bash
   dalp mcp add
   ```

4. Restart the assistant after configuration changes.

### Authentication required [#authentication-required]

The CLI session may be missing or expired.

```bash
dalp login --url https://your-platform.example.com
```

Restart the assistant after login so it can use the refreshed CLI session.

### Permission denied [#permission-denied]

The authenticated account lacks the required role for the operation. Check the current account and ask a platform administrator to grant the needed role.

```bash
dalp whoami --format json
dalp system access-manager roles-list --format json
```

## Next steps [#next-steps]

* Read the [CLI AI agent integration guide](/docs/developer-guides/cli/ai-agents) for developer and scripting patterns.
* Use the [CLI command reference](/docs/developer-guides/cli/command-reference) to check exact command names and options.
* Review [user onboarding](/docs/user-guides/user-management/user-onboarding) before asking an assistant to help with identity workflows.
* Review the [compliance overview](/docs/user-guides/compliance/overview) before asking an assistant to prepare compliance changes.