> ## Documentation Index
> Fetch the complete documentation index at: https://darwin.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashlane

> Resolve a Dashlane credential or secret through an authorized local or service runner.

Darwin can use a Dashlane vault item as a just-in-time authentication source when an authorized Dashlane CLI runner is available. The item stays in Dashlane and is referenced with a `dl://` URI.

<Note>
  This adapter is a planned preview. It is not available in the production API or MCP tool set yet.
</Note>

## Use the CLI boundary

Dashlane's public API is read-only and does not expose members' vault passwords. Darwin therefore does not use that API to fetch login credentials. The planned adapter invokes the Dashlane CLI inside the user's or organization's authorized runner and consumes only the resolved value needed for the current Action.

```text theme={null}
bounded authentication interaction -> dl:// secret reference -> authorized CLI runner
                                   -> transient credential -> provider authentication
                          -> discard secret value
```

The runner may use an interactive personal login or an organization-approved service device. Darwin does not collect the user's Dashlane master password, SSO credential, recovery material, or vault export.

## Keep resolution narrow

* Prefer an immutable item identifier over title-based lookup.
* Bind the item reference to the current provider, AI, capability revision, and requested scopes.
* Exclude the resolved value from model context, Action results, logs, traces, analytics, and webhooks.
* Let Dashlane continue to own item sharing, rotation, revocation, and deletion.

See the [Dashlane CLI documentation](https://cli.dashlane.com/) and its [`dl://` secret references](https://cli.dashlane.com/personal/secrets/read) for the provider's current behavior.