Devolens / Cryptolens, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Devolens / Cryptolens account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Developer Tools
- Connects with a key
- 10 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Devolens / Cryptolens is
Devolens provides the Cryptolens software licensing API for managing products, license keys, customers, usage analytics, and entitlements.
You paste in a key from your own Devolens / Cryptolens account. It is kept encrypted, and you can withdraw it from inside Devolens / Cryptolens whenever you like.
One message in, the work done in Devolens / Cryptolens.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Devolens / Cryptolens. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Devolens / Cryptolens account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Devolens / Cryptolens
These are the ready-made tools your AI employee already has in Devolens / Cryptolens. It is not limited to them, but it never has to be taught these.
- Get License KeyRetrieve one license key and optional activation metadata by its product ID and key string. The token must enable the Get Key method.
- List CustomersSearch or list customers visible to the connected Cryptolens account, including reseller-visible customer groups returned by the API. The token must enable the Get Customers method
- List Daily Usage AggregatesReturn one page of daily Cryptolens usage aggregates, optionally filtered by product and inclusive date range. Pass nextcursor back with the same filters to continue forward. The t
- List License KeysList and search one page of license keys for a Cryptolens product. Call List Products first when the product ID is unknown, then pass nextcursor back to continue through additional
- List License TemplatesReturn the license templates available to the connected Cryptolens account. The token must enable the Get License Templates method.
- List License UsersReturn registered Cryptolens license users, optionally limited to one customer. The token must enable the UserAuthAdmin method group.
- List MessagesReturn Cryptolens account messages, optionally filtered by channel or creation time. The token must enable the Get Messages method.
- List ProductsReturn the Cryptolens products visible to the connected access token. Use this first to obtain product IDs required by license-key tools. The token must enable the Get Products met
- List ResellersSearch or list resellers visible to the connected Cryptolens account. The token must enable the Reseller method group.
- List Web API LogsInspect one page of Cryptolens Web API request logs with optional product, license-key, machine, event, and time filters. Pass nextcursor back to continue when one is returned. The
You stay the boss of your Devolens / Cryptolens account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Devolens / Cryptolens account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Devolens / Cryptolens is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Devolens / Cryptolens and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Devolens / Cryptolens
- Can an AI employee really work inside Devolens / Cryptolens?
- Yes. It signs in to your own Devolens / Cryptolens account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Devolens / Cryptolens?
- No. Nothing moves and nothing is replaced. Your records stay in Devolens / Cryptolens, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Devolens / Cryptolens account?
- You paste in a key from your own Devolens / Cryptolens account. It is kept encrypted, and you can withdraw it from inside Devolens / Cryptolens whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Devolens / Cryptolens?
- It has 10 ready-made tools in Devolens / Cryptolens today, among them Get License Key, List Customers and List Daily Usage Aggregates. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Devolens / Cryptolens and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Devolens / Cryptolens and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Devolens / Cryptolens?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Devolens / Cryptolens is written down with what it did and when.