ElevenLabs’ current Music API terms prohibit customers from making API access available to third parties unless ElevenLabs has authorized them as resellers. An API key proves which account made a request but does not grant permission to sell the model behind it.
A paid plan may give you commercial rights for finished Eleven Music output, but those rights govern tracks rather than customer access to generation. Using the API inside your own production workflow is one activity, while letting paying users enter prompts and receive songs is another.
The current music rights table marks reseller rights as prohibited across every self-serve plan, including Scale and Business. Those plans may still include API access, while Enterprise Music Lite and full Enterprise list reseller rights as custom, not automatic.
Adding substantial workflow features may move a product beyond that narrow reseller definition, but it does not create permission by itself. The broader API restriction still applies whenever a third party receives model access through your product. The signed agreement needs to describe the actual route from user prompt to generated file.
A studio that calls the API internally and delivers a finished jingle does not hand its client generation access. A SaaS product that lets the client choose lyrics, style, duration, and reruns looks materially different. That second design offers direct end-user generation access, even when every request passes through your server.
Server-side routing is still essential for security. API credentials are intended for the account holder, must remain confidential, and should never sit in browser code or a mobile application. Hiding the key protects it from theft, but it does not settle the licensing question.
Each end user must accept a written or clickwrap agreement before receiving access under the published OEM structure. Those terms must match ElevenLabs’ restrictions, name it as a third-party beneficiary, permit required data processing, and avoid conflicting performance promises.
The standard OEM definition is narrow, describing an end user as a customer using the solution for internal business operations. A public creator app serving individuals should not assume that default language covers its audience without a custom agreement.
You remain responsible for end-user violations, required consents, reasonable security, and stopping unauthorized use. Your privacy notice must accurately explain what user information reaches ElevenLabs and other parties. ElevenLabs can suspend an end user whose continued activity threatens the service or other customers.
The distribution chain stops at your customer because the published terms do not allow that customer to expose the same bundled service to another group. You also provide first-line support, while ElevenLabs has no obligation to support your users directly.
Authorized resellers and companies whose main commercial product is AI music creation face a visible branding condition. Their bundled service and related promotion must prominently display ElevenLabs branding, so a silent white-label launch may conflict with the required structure.
A track repository creates another rights layer. The music terms define libraries and repositories as arrangements that collect output for licensing or availability to third parties. Self-serve plans prohibit that activity, while Enterprise plans treat it as a custom right separate from ordinary API access.
Product changes can quietly outrun the agreement. An internal tool may later gain customer logins, a marketplace, team subaccounts, or an export catalog. Each addition can alter who receives access and what they may do with output, even when the endpoint and API key stay unchanged.
The published OEM terms also allow compliance verification during authorization and for three years afterward. Ordinary inspections require at least ten business days’ notice and normally occur no more than once per calendar year. Material noncompliance can justify additional checks.
Keep the signed order, applicable term versions, accepted end-user agreements, permission records, usage logs, and suspension history together. Record which product feature created each request and which customer received its output. Those records let the deployed service be compared with the authorization ElevenLabs actually granted.
A paid plan may give you commercial rights for finished Eleven Music output, but those rights govern tracks rather than customer access to generation. Using the API inside your own production workflow is one activity, while letting paying users enter prompts and receive songs is another.
The current music rights table marks reseller rights as prohibited across every self-serve plan, including Scale and Business. Those plans may still include API access, while Enterprise Music Lite and full Enterprise list reseller rights as custom, not automatic.
A user-facing generator becomes a different product
The API terms prohibit reselling, repackaging, redistributing, sublicensing, or otherwise making access available to another party without authorization. ElevenLabs separately defines a reseller as a thin wrapper around its models or an aggregator that lists them beside competing models. Cosmetic interface work does not create a new service.Adding substantial workflow features may move a product beyond that narrow reseller definition, but it does not create permission by itself. The broader API restriction still applies whenever a third party receives model access through your product. The signed agreement needs to describe the actual route from user prompt to generated file.
A studio that calls the API internally and delivers a finished jingle does not hand its client generation access. A SaaS product that lets the client choose lyrics, style, duration, and reruns looks materially different. That second design offers direct end-user generation access, even when every request passes through your server.
Server-side routing is still essential for security. API credentials are intended for the account holder, must remain confidential, and should never sit in browser code or a mobile application. Hiding the key protects it from theft, but it does not settle the licensing question.
Authorized access carries contracts and controls
The published OEM terms apply only when the underlying agreement expressly permits you to bundle, sublicense, or make the service available. Permission needs a product scope accepted by ElevenLabs in writing, since a pricing page or functioning endpoint is not approval.Each end user must accept a written or clickwrap agreement before receiving access under the published OEM structure. Those terms must match ElevenLabs’ restrictions, name it as a third-party beneficiary, permit required data processing, and avoid conflicting performance promises.
The standard OEM definition is narrow, describing an end user as a customer using the solution for internal business operations. A public creator app serving individuals should not assume that default language covers its audience without a custom agreement.
You remain responsible for end-user violations, required consents, reasonable security, and stopping unauthorized use. Your privacy notice must accurately explain what user information reaches ElevenLabs and other parties. ElevenLabs can suspend an end user whose continued activity threatens the service or other customers.
The distribution chain stops at your customer because the published terms do not allow that customer to expose the same bundled service to another group. You also provide first-line support, while ElevenLabs has no obligation to support your users directly.
Authorized resellers and companies whose main commercial product is AI music creation face a visible branding condition. Their bundled service and related promotion must prominently display ElevenLabs branding, so a silent white-label launch may conflict with the required structure.
The signed scope must match the product you ship
The contract should identify who can generate, who receives the files, and whether users may publish, sublicense, or sell them. It should name expected volume, territories, data flows, support duties, branding, and prohibited uses, because vague permission leaves the difficult rights unresolved.A track repository creates another rights layer. The music terms define libraries and repositories as arrangements that collect output for licensing or availability to third parties. Self-serve plans prohibit that activity, while Enterprise plans treat it as a custom right separate from ordinary API access.
Product changes can quietly outrun the agreement. An internal tool may later gain customer logins, a marketplace, team subaccounts, or an export catalog. Each addition can alter who receives access and what they may do with output, even when the endpoint and API key stay unchanged.
The published OEM terms also allow compliance verification during authorization and for three years afterward. Ordinary inspections require at least ten business days’ notice and normally occur no more than once per calendar year. Material noncompliance can justify additional checks.
Keep the signed order, applicable term versions, accepted end-user agreements, permission records, usage logs, and suspension history together. Record which product feature created each request and which customer received its output. Those records let the deployed service be compared with the authorization ElevenLabs actually granted.
