Skip to content
Log inSign up
Contact salesLog in

CLI Terms

Last updated: August 24, 2026

These ElevenLabs CLI Terms (these “CLI Terms”) apply to your (“you”, “your” or “Customer”) access to and use of the Services through the CLI. They supplement your existing agreement with ElevenLabs or, if no separate agreement exists, the ElevenLabs Terms of Service applicable to you (either, the “Underlying ElevenLabs Agreement”). Your use of the CLI is also subject to our Prohibited Use Policy. Our processing of personal data in connection with the CLI is governed by the data protection terms of your Underlying ElevenLabs Agreement, including the DPA where one applies to you, and our Privacy Policy describes how we process personal data where we act as controller. Where you use the CLI to access a Service that is subject to its own Service-Specific Terms (“Service-Specific Terms”), those terms continue to apply to that Service, and these CLI Terms supplement them. Capitalized terms used but not defined in these CLI Terms have the meanings set forth in the Underlying ElevenLabs Agreement. 

If you do not have a signed written agreement with ElevenLabs, you accept these CLI Terms by installing or using the CLI, and you may not use the CLI if you do not agree to them or lack the authority to agree. 

  1. The CLI.
    1. CLI. The “CLI” is the ElevenLabs command-line interface, which you install and run in your own environment to access and operate the Services from a terminal, including by managing configuration as code in local files and synchronizing it with the Services, and by building, deploying, and managing AI agents as code. This description does not create any representation, warranty, or other commitment as to the CLI. 
    2. Commands. The CLI exposes ElevenLabs API endpoints published in our OpenAPI specification as commands. We do not warrant that any particular endpoint, capability, or Service is available through the CLI, that the CLI is functionally equivalent to our API, dashboard, or SDKs, or that any command will remain available. 
    3. Availability. We may introduce or change fees or usage limits applicable to use of the Services through the CLI on notice in accordance with the Underlying ElevenLabs Agreement. Usage of the Services initiated through the CLI is otherwise billed, and subject to the same rate, concurrency, and entitlement limits, as equivalent usage initiated through our dashboard or API. We may release, change, deprecate, or discontinue versions of the CLI. 
    4. Open Source. The CLI is made available under the MIT License, and your rights in the CLI software are governed by that license. Nothing in these CLI Terms limits any rights you may have under, or grants you rights that supersede, the terms of the applicable open-source license. That license governs the CLI software and does not grant any right to access or use the Services, which are governed by the Underlying ElevenLabs Agreement and these CLI Terms. 
  3. Credentials and Attribution.
    1. Authentication. The CLI authenticates using the methods we make available, which may include OAuth-based browser-based authorization in which you select a workspace and scopes, a device-code flow for headless or remote environments, and an API key you supply. We may modify, replace, or discontinue any authorization method at any time.
    2. Your Credentials. You are responsible for each credential used with the CLI, including for the workspace and scopes you authorize, for issuing, storing, rotating, and revoking API keys and tokens, and for restricting each credential to the permissions the intended commands require. 
    3. Attribution. Each command run through the CLI, and all resulting access to and use of the Services, is attributed to the account and workspace associated with the credential used. That activity is treated as your action and is your responsibility, whether or not you authorized it and whether initiated by a person or by a script, a continuous integration or deployment pipeline, a coding assistant, or any other AI tool or automated process (each, an “Automated Process”). 
  5. Configuration Files. The CLI creates and reads configuration files in your environment, including registries, configuration directories, and environment-specific configurations. You are responsible for the contents of those files and for anything you commit to a version control system or otherwise distribute, including prompts, tool and webhook configurations, and any credential, secret, or reference to either. You will not commit or otherwise distribute any credential or secret in a configuration file or other artifact, and you will promptly revoke and rotate any credential you have reason to believe has been exposed.
  6. Commands and Automated Use.
    1. Effect of Commands. CLI commands can create, modify, overwrite, and delete resources in the Services, including agents, tools, and tests, together with their configuration. In particular, pushing replaces the configuration held in the Services with your local configuration, and pulling with the update option replaces your local configuration with the configuration held in the Services. These effects may be immediate and irreversible, and configuration and resources may be permanently lost. We have no obligation to restore or recover them. 
    2. Your Responsibilities. You are responsible for the scope and effect of each command you run, for reviewing changes before applying them, for maintaining your own backups of configuration you wish to retain, and for verifying that each command achieved the result you intended. Reviewing changes includes using any preview, diff, or dry-run option we make available. 
    3. Automated and Agent-Driven Use. If you run the CLI through an Automated Process, you are responsible for the credentials it holds, for every change it makes, for any use of an option that suppresses a confirmation prompt, and for separating development, staging, and testing activity from your production workspaces, agents, and phone numbers. 
  8. Templates and Generated Files. The CLI provides templates and generates code, configuration, and other files. These are starting points provided for convenience, and we do not warrant that any of them is suitable for your intended use, secure, or compliant with any law or standard applicable to you. You are responsible for reviewing, testing, and configuring them before use. 
  9. Scope of Our Security and Data Commitments. Our security and data protection commitments under the Underlying ElevenLabs Agreement, including the DPA and any information security addendum or exhibit forming part of it, where each applies to you, apply within systems we control to Customer Content or Content, as applicable. They do not apply to your environment, including your machines, repositories, version control systems, and any Automated Process, or to any configuration, credential, or Customer Content or Content held in any of them. 
  10. Your Content. Data, information, and material you provide to the Services through the CLI, and any Output generated in connection with the CLI, constitute Content or Customer Content, as applicable, and may be used by us as provided in the Underlying ElevenLabs Agreement. You will not use the CLI to transmit to us any data you are prohibited from submitting under the Underlying ElevenLabs Agreement or the applicable Service-Specific Terms, including Prohibited Data as defined in the applicable Service-Specific Terms and protected health information, except as permitted by an executed business associate agreement or as we have otherwise expressly agreed in writing, and will not permit any person or Automated Process acting on your behalf or using your credentials to do so. 
  11. General.
    1. Service-Specific and Model-Specific Terms. Your access to and use of particular Services or models through the CLI may be subject to additional terms we post for them (“Model-Specific Terms” and, together with the Service-Specific Terms, the “Applicable Service Terms”), which supplement and form part of these CLI Terms as they relate to your use of the CLI. 
    2. Beta Services. To the extent we designate the CLI, or any CLI feature or command, as alpha, beta, pilot, preview, or a similar designation, the Beta Services provisions of the Underlying ElevenLabs Agreement apply to it, or, if you are subject to the ElevenLabs Terms of Service, the Beta Services Addendum applies to it. Those provisions prevail over these CLI Terms in the event of a conflict, solely as to the CLI or any CLI feature or command. Your decision to purchase or use the Services was not and is not contingent on the availability of the CLI or of any CLI feature or command. 
    3. Suspension. We may suspend or restrict your access to the Services through the CLI, or disable a credential used with the CLI, where we reasonably determine this is necessary to address a violation of these CLI Terms, the Prohibited Use Policy, or the Underlying ElevenLabs Agreement, a compromised or misused credential, or a risk to the security, integrity, or availability of the Services. Where practicable we will notify you first and give you a reasonable opportunity to resolve the issue, and we will restore access promptly once it is resolved. This Section is in addition to any suspension or termination right under the Underlying ElevenLabs Agreement.
    4. Support. Our support commitments under the Underlying ElevenLabs Agreement apply to the Services. They do not extend to the CLI as installed, configured, or run in your environment, or to any third-party software or dependency required to run it.
    5. Order of Precedence. If there is a conflict, the following order applies to your access to and use of the Services through the CLI: (a) any term of the Underlying ElevenLabs Agreement or an Order Form that expressly addresses the CLI; (b) the Applicable Service Terms, other than the ElevenAPI Terms; (c) these CLI Terms; and (d) the remainder of the Underlying ElevenLabs Agreement. Except as expressly set forth herein, these CLI Terms do not modify the confidentiality, indemnification, or limitation of liability provisions of the Underlying ElevenLabs Agreement. 
    6. Updates. We may update these CLI Terms. Updates take effect when we post them, except that, if you have a signed written agreement with ElevenLabs, an update that materially reduces your rights takes effect 30 days after we notify you, or at your next renewal if earlier. Updates required by law, or that we reasonably determine are necessary to address a legal, safety, or security risk, take effect immediately.

Create with the highest quality AI Audio

Sign up