ElevenAPI Terms
Last updated: October 09, 2026
These ElevenAPI Terms (“ElevenAPI Terms”) govern your (“you,” “your,” or “Customer”) use of the API, MCP Features under Exhibit 1, the CLI under Exhibit 2, and the Music Service through the API under Exhibit 3. Each Exhibit forms part of these ElevenAPI Terms and defines the functionality it covers. The API and the functionality covered by each Exhibit that applies to you are each “Covered Functionality.” Sections 1 through 6 apply to all Covered Functionality, and each applicable Exhibit applies in addition to them. These ElevenAPI Terms supplement your written agreement with ElevenLabs or, if none exists, the ElevenLabs Terms of Service applicable to you (either, the “Underlying ElevenLabs Agreement”), which gives meaning to capitalized terms not defined here. Absent a signed written agreement, you accept these ElevenAPI Terms by accessing or using the API, enabling or using an MCP Feature, or installing or using the CLI. You may not do any of those things if you do not agree to these ElevenAPI Terms or lack authority to agree.
1. The API.
1.1. Description and Documentation. The “API” comprises ElevenLabs’ application programming interfaces, including REST, streaming, and WebSocket endpoints and official software development kits (“SDKs”), for accessing and operating the Services programmatically. “Documentation” means ElevenLabs’ then-current technical and functional documentation for the Services and Covered Functionality, including the documentation published at https://elevenlabs.io/docs and any documentation ElevenLabs otherwise provides to you. You shall follow the Documentation, including the limits, intervals, formats, and integration requirements it specifies, and ElevenLabs may update it from time to time.
1.2. Applicable Service Terms. ElevenLabs publishes Service-Specific Terms and Model-Specific Terms for particular Services and models, including the ElevenAgents Terms and the ElevenLabs Music Terms. Those terms, other than these ElevenAPI Terms, are “Applicable Service Terms” and form part of these ElevenAPI Terms solely as to the Services and models you access.
1.3. Availability and Versions. Availability depends on your plan, entitlements, and region. An isolated regional environment is a separate workspace with its own endpoints and credentials and may offer fewer capabilities. ElevenLabs does not warrant the current or continued availability of any Covered Functionality. Usage of the Services initiated through any Covered Functionality is billed under your plan or Order Form and counts toward the rate, concurrency, and entitlement limits applicable to you. Equivalent usage is billed and limited alike however it is, whether through Covered Functionality or the dashboard.
1.4. Open Source. Applicable open-source licenses, including the MIT License, govern SDKs and other software and material ElevenLabs provides as part of Covered Functionality. These ElevenAPI Terms neither limit nor supersede those licenses. Those licenses grant no right to access or use the Services.
2. Credentials and Attribution.
2.1. Security. You are responsible for issuing, securing, rotating, and revoking credentials for Covered Functionality, including keys, OAuth client secrets and refresh tokens, webhook signing secrets, tokens, and signed access URLs, and for configuring appropriate scope, quota, expiry, and network restrictions. You shall not share credentials outside your organization, expose them in third-party-accessible clients or artifacts, or commit or distribute any credential or secret. You shall use API keys only in environments you control and through the methods the Documentation designates. You shall promptly revoke and replace any credential you have reason to believe is exposed, and promptly notify ElevenLabs of any unauthorized access to your account or workspace.
2.2. Attribution. API calls, commands, and resulting Services activity are attributed to the account and workspace whose credential is used and are your responsibility, whether or not you authorized them and whether initiated by a person, script, pipeline, coding assistant, or other automated process (“Automated Process”). This Section 2.2 does not apply to API activity resulting from ElevenLabs’ breach of its security obligations under the Underlying ElevenLabs Agreement, and that exception applies solely to API activity.
2.3. Customer Applications. A “Customer Application” is any application, product, or service of yours through which you access the Services through the API, and has the meaning given in the Underlying ElevenLabs Agreement where that agreement defines it. You are responsible for each Customer Application, including for authenticating and authorizing its users and for ensuring that a user cannot access Services resources you have not authorized that user to access. Your credentials are not a substitute for access controls in your own systems.
3. Integrations.
3.1. Limits and Compatibility. Your API integrations must tolerate additive changes to responses, and must not rely on undocumented behavior.
3.2. Results and Webhooks. Where you choose to receive results by webhook, you shall operate and secure your receiving endpoints, verify delivery signatures before acting, and handle duplicate deliveries idempotently, and you bear the risk of unverified deliveries. ElevenLabs may disable repeatedly failing or unreachable endpoints. However you collect results, you shall retrieve and store them before signed URLs expire, and, except as the Documentation expressly provides, ElevenLabs need not retain results or reissue access to them.
4. Content and Data.
4.1. Scope. Materials you submit and Output generated through any Covered Functionality are Customer Content or Content under the Underlying ElevenLabs Agreement and may be used as that agreement provides. ElevenLabs’ security and data-protection commitments, including the applicable DPA and security terms, apply to Customer Content and Content within the systems ElevenLabs controls. They do not apply to any system or environment you or a third party controls, including any Automated Process and any third-party server, client, or application you connect to or use with the Services, or to any credential, configuration, or content held in or transmitted to any of them at your direction.
4.2. Restrictions. You shall not permit any person or Automated Process acting for you or using your credentials to take any action these ElevenAPI Terms prohibit. You may transmit protected health information through the API only as permitted by an executed business associate agreement, by applicable law, or by ElevenLabs’ express written agreement, and you shall not transmit it through any other Covered Functionality except as the applicable Exhibit expressly permits.
5. Suspension and Support.
5.1. Suspension. Suspension is governed by the Underlying ElevenLabs Agreement, except that its notice and cure periods do not apply where ElevenLabs disables an individual credential, or restricts an individual Covered Functionality, to address credential compromise or misuse or a risk to the security, integrity, or availability of the Services.
5.2. Support. ElevenLabs’ support commitments under the Underlying ElevenLabs Agreement, where you have them, apply to the Services. They do not extend to any Customer Application, integration, SDK, or other software or component as implemented, configured, or run in your environment, or to any third-party software, service or dependency required to run it.
6. Updates. ElevenLabs may update these ElevenAPI Terms, including any Exhibit, prospectively. An update that materially reduces your rights takes effect 30 days after ElevenLabs notifies you, and other updates take effect when posted, except that an update required by law, or that ElevenLabs reasonably determines is necessary to address a legal, regulatory, safety, or security risk, takes effect immediately and ElevenLabs will notify you of it promptly.
EXHIBIT 1: MCP FEATURES
This Exhibit 1 applies to MCP Features, whether enabled through the ElevenLabs dashboard, the API, or an SDK. “Customer AI Agent” has the meaning given in the ElevenAgents Terms.
1. Description. “MCP” means Model Context Protocol. An “MCP Feature” is functionality that connects either: (a) an MCP server you or a third party operates (an “External MCP Server”) to the Services, so that a Customer AI Agent can use the tools or data that server exposes; or (b) an MCP-compatible application or assistant you use or authorize (an “MCP Client”) to the “ElevenLabs MCP Server,” so that the MCP Client can read, create, configure, or delete resources in your workspace. Establishing either connection is a “Connection.”
2. Availability and Data. MCP Features are unavailable where you have elected Zero Retention Mode or require HIPAA compliance, unless ElevenLabs expressly agrees otherwise in writing. Neither enablement of an MCP Feature nor an exception under Section 4.2 overrides this restriction. You shall not transmit through a Connection data prohibited by the Underlying ElevenLabs Agreement or the ElevenAgents Terms, including Prohibited Data and protected health information. You configure conversation retention, redaction, and related privacy controls described in the Documentation.
3. Enablement and Authority. MCP Features are disabled by default and enabled at workspace level, including by non-administrators. Enablement, acceptance of these ElevenAPI Terms for MCP, and Connections by anyone using your workspace or credentials bind you. You control who may enable features, establish or modify Connections, and approve tool calls. A Connection authorizes the Services and, within granted scopes, MCP Clients to act for you, and their actions are your actions. You represent that you have all rights, consents, and authority necessary for Connections, access to connected systems and data, and ElevenLabs’ transmission, receipt, and processing of that data.
4. External MCP Servers. You are responsible for each External MCP Server, for its operator, and for everything it does in connection with the Services. You shall: (a) vet, configure, and monitor each External MCP Server and its security, availability, lawfulness, and behavior; (b) set tool-approval controls appropriate to the risk of each tool, including requiring approval before a tool writes, deletes, transmits, or otherwise alters data; (c) limit the data exchanged with each External MCP Server to what the relevant tool requires, and remain responsible for that data; (d) guard against prompt injection and other manipulation originating from an External MCP Server, its tool definitions, or the content it returns; (e) secure the credentials, secrets, tokens, headers, and connection details used for each Connection, and use encrypted transport; and (f) promptly notify legal@elevenlabs.io of any vulnerability, compromise, or unauthorized access affecting an External MCP Server that is or has been connected to the Services. An operator may change the tools and capabilities its server exposes without notice, and you bear the consequences of any such change.
5. MCP Clients. Connecting an MCP Client to the ElevenLabs MCP Server authorizes that MCP Client to act for you within the scope you grant at sign-in. You are responsible for selecting each MCP Client, for the persons you permit to connect it, for reviewing tool calls before approving them, including destructive actions, and for revoking access when it is no longer required.
6. Third-Party Services. External MCP Servers and MCP Clients are third-party services whose operators and providers are not ElevenLabs’ subcontractors, subprocessors, or agents. ElevenLabs does not provide, operate, endorse, verify, vet, secure, monitor, support, or troubleshoot them and is not responsible for their operators’ or providers’ acts or omissions. Documentation references to servers, clients, or directories are not recommendations or approvals.
EXHIBIT 2: ELEVENLABS CLI
This Exhibit 2 applies to the CLI.
1. Description and Access. The “CLI” is ElevenLabs’ locally installed command-line interface for operating the Services, including synchronizing local configuration and managing agents as code. It exposes published OpenAPI endpoints as commands, without warranty of availability, continued availability, or parity with the API, dashboard, or SDKs. Authentication may use browser-based OAuth, a device code, or an API key you supply. ElevenLabs may change, replace, or discontinue any authentication method.
2. Configuration and Commands. You are responsible for local configuration files and anything committed or distributed from them. Commands may create, modify, overwrite, or permanently delete resources and configurations. Pushing replaces the configuration held in the Services with your local configuration, and pulling with the update option does the reverse. Effects may be immediate and irreversible, and ElevenLabs need not restore or recover them. You shall review each command’s scope and changes before execution, using available preview, diff, or dry-run tools, maintain necessary backups, and verify results. Section 2.1 (Security) governs credential security and exposure.
3. Automated Use. You are responsible for any use of an option that suppresses a confirmation prompt. You are also responsible for separating development, staging, and testing activity from your production workspaces, agents, and phone numbers.
4. Generated Files. Templates and the code, configuration, and other files the CLI generates are starting points provided for convenience. ElevenLabs does not warrant that any of them is suitable for your intended use, secure, or compliant with any law or standard applicable to you. You shall review, test, and configure them before use.
EXHIBIT 3: ELEVENLABS MUSIC API
This Exhibit 3 applies to your use of the Music Service through the API, including through any tool or interface ElevenLabs provides for accessing the API. The ElevenLabs Music Terms supply additional definitions.
1. Access and Distribution. Unless you are an Authorized Reseller, you shall not resell, repackage, redistribute, sublicense, or otherwise make API access to the Music Service available to any third party. Where you or your end users distribute Music Output on a streaming platform, digital service provider, or content-hosting service, you are responsible for complying with that platform’s policies on the disclosure of AI-generated content, including any labeling, metadata, or tagging requirements.
