Devolens / Cryptolens
for LuumenAI

Read Cryptolens licensing state — keys, customers, usage, and API logs

Ask about a license without leaving the terminal. Luumen connects to Cryptolens with an API key and reads your products, license keys, templates, customers, license users, and resellers. Check a single key with DEVOLENS_GET_LICENSE_KEY, trace activation problems through DEVOLENS_LIST_WEB_API_LOGS, and review consumption with DEVOLENS_LIST_DAILY_USAGE_AGGREGATES. Read-only: no tool here changes licensing state.

Book a DemoDownload Luumen

The Devolens / Cryptolens toolbox

10 tools, all read-only. They answer instantly, and every call is logged.

  • ReadGet License KeyRetrieve one license key and optional activation metadata by its product ID and key string.
  • ReadList CustomersSearch or list customers visible to the connected Cryptolens account, including reseller-visible customer groups returned by the API.
  • ReadList Daily Usage AggregatesReturn one page of daily Cryptolens usage aggregates, optionally filtered by product and inclusive date range.
  • ReadList License KeysList and search one page of license keys for a Cryptolens product.
  • ReadList License TemplatesReturn the license templates available to the connected Cryptolens account.
  • ReadList License UsersReturn registered Cryptolens license users, optionally limited to one customer.
  • ReadList MessagesReturn Cryptolens account messages, optionally filtered by channel or creation time.
  • ReadList ProductsReturn the Cryptolens products visible to the connected access token.
  • ReadList ResellersSearch or list resellers visible to the connected Cryptolens account.
  • ReadList Web API LogsInspect one page of Cryptolens Web API request logs with optional product, license-key, machine, event, and time filters.

Questions

How does LuumenAI connect to Devolens / Cryptolens?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Devolens / Cryptolens on its own?

No. Every one of the 10 tools LuumenAI has for Devolens / Cryptolens is read-only, so it can answer questions from Devolens / Cryptolens but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.

Who gets access to the integration?

You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.

Is there an audit trail?

Every call to Devolens / Cryptolens is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

All integrations
GitHubRepos, actions, and runbook code as context and as actions.GitLabMerge requests and pipelines proposed, triggered, and rolled back.BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.

Put Devolens / Cryptolens to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a DemoDownload Luumen