Sure, so there is no concept of automations for the license management. Think of how other services out there like GitHub use api_keys to allow people to build automation routines and tools on top of GitHub API. Perhaps allow for creation of restricted api keys that we can control different permissions for. At the moment the API Key is an all access key to the account and I agree it's not a good idea to hand it out to clients.
API Key can only be used from max of 3 IPsAnswered
Imagine a simple scenario. We have a license key with 100 activations. That means that in a typical corporate environment client will deploy our tool to up to 100 different machines. That's assuming they don't want to use the TurboFloat. Let's say these are machine locked licenses, and clients deploy to 100 computers, but over time they return their leased computers, reinstall them via format or some other stuff. It basically means that some of these license activations become invalid and it would be good to deactivate them to cleanup their pool of licenses.
I could develop some kind of interface using the Web APIs that are available to allow our clients to clean up their own license activations and deactivate computers that no longer need the license, but at the moment such tool that would interact with LimeLMs APIs can only be used from max 3 different IPs. That means I can give that tool to one or two clients. Any reason why there is a limit to the API_KEY to only be allowed to be used from 3 IPs?
Answer
I could develop some kind of interface using the Web APIs that are available to allow our clients to clean up their own license activations and deactivate computers that no longer need the license
Yikes, don't do that. Giving a customer this tool would give them complete control of your account.
The API key is a password that controls your account. Treat it as such.
One of the reasons we limited where API keys could be used is to prevent this exact scenario.