DeepL Pro License Terms and Conditions
The only changes in this update are cosmetic: links to DeepL MCP endpoints were updated from http:// to https:// for secure connections. No substantive terms changed.
Cosmetic change: formatting, typos, or contact details.
| 832 | 832 | \*DeepL reserves the right to change or remove the free of charge DeepL Voice allowance at its sole discretion. |
| 833 | 833 | |
| 834 | 834 | ### DeepL MCP (Remote Model Context Protocol Server) |
| 835 | 835 | |
| 836 | 836 | DeepL MCP is a hosted endpoint that enables third-party AI applications to access DeepL translation and writing functions via the Model Context Protocol ("MCP"). Compatible AI applications can use DeepL MCP to translate text and documents, improve text with DeepL Write (if applicable), and retrieve the languages, glossaries, style rules, and writing settings available to the user. |
| 837 | 837 | |
| 838 | Access to DeepL MCP is available at [mcp.deepl.com](http://mcp.deepl.com/) for Customers. The Internal User authorizes the AI application by signing in with their DeepL account (OAuth 2.1). Access reflects the signed-in Internal User's individual account permissions. | |
| 838 | Access to DeepL MCP is available at [mcp.deepl.com](https://mcp.deepl.com/) for Customers. The Internal User authorizes the AI application by signing in with their DeepL account (OAuth 2.1). Access reflects the signed-in Internal User's individual account permissions. | |
± CHANGEDMCP endpoint link now uses HTTPS The link to mcp.deepl.com was updated from a plain http:// address to a secure https:// address. This is just a technical update to the URL format, not a change in terms. | ||
| 839 | 839 | |
| 840 | 840 | DeepL MCP provides the following tools, equivalent to the corresponding DeepL functions: |
| 841 | 841 | |
| 842 | 842 | | |
| 843 | 843 | **Tool** |
| 844 | 844 | |
| 1159 | 1159 | The DeepL API Pro and DeepL API Free are designed to process at least 600 characters per minute and per Customer; exceeding use may be limited, and Customers may encounter a 429 "Too Many Requests" error message, as described in the documentation. |
| 1160 | 1160 | |
| 1161 | 1161 | Applications using the DeepL API Pro or DeepL API Free should implement a mechanism to handle such responses accordingly and, if appropriate, to try again later. A mechanism increasing the delay for another request exponentially is recommended. |
| 1162 | 1162 | |
| 1163 | 1163 | ### DeepL MCP for API (Remote Model Context Protocol Server) |
| 1164 | 1164 | |
| 1165 | If and to the extent DeepL MCP use is included in an API plan, usage of the Services via DeepL MCP authenticated with Customer's API key constitutes use of the API. In that case the DeepL API can be accessed via DeepL's hosted Model Context Protocol endpoint at [mcp-api.deepl.com](http://mcp-api.deepl.com/), using the same API key as [api.deepl.com](http://api.deepl.com/). | |
| 1165 | If and to the extent DeepL MCP use is included in an API plan, usage of the Services via DeepL MCP authenticated with Customer's API key constitutes use of the API. In that case the DeepL API can be accessed via DeepL's hosted Model Context Protocol endpoint at [mcp-api.deepl.com](https://mcp-api.deepl.com/), using the same API key as [api.deepl.com](https://api.deepl.com/). | |
± CHANGEDMCP API endpoint links now use HTTPS The links to mcp-api.deepl.com and api.deepl.com were updated from http:// to https:// addresses. This is just a technical update to the URL format, not a change in terms. | ||
| 1166 | 1166 | |
| 1167 | 1167 | Usage via DeepL MCP is metered and billed under the Customer's DeepL API subscription on the same basis as direct API usage. Character limits, file size limits, supported formats, and rate limits are the same as for the DeepL API. |
| 1168 | 1168 | |
| 1169 | 1169 | DeepL MCP provides the following tools, equivalent to the corresponding DeepL functions: |
| 1170 | 1170 | |
| 1171 | 1171 | | |