NetLicensing
for LuumenAI

Read your NetLicensing catalog and issue licenses as approved steps

Connect NetLicensing and Luumen can read your products, product modules, license templates, licensees, licenses, and transactions on request. Ask who holds which license, or what a template allows. When a change is needed — a new licensee, a license issued from a template, a bundle updated — Luumen shows the plan first and, by default, waits for your approval. Authentication uses an API key.

Book a DemoDownload Luumen

The NetLicensing toolbox

21 tools: 3 read, 18 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet ResourceGet one product, product module, license template, licensee, license, transaction, or bundle by its NetLicensing number.
  • ReadList Licensing OptionsReturn the supported licensing models and license types used when configuring product modules and license templates.
  • ReadList ResourcesList one page of products, product modules, license templates, licensees, licenses, transactions, or bundles for the connected vendor.
  • WriteCheck In Licensee SessionReturn and release a NetLicensing floating-license session for a licensee and return the validation results and provider cache TTL when supplied. Approval by default
  • WriteCheck Out Licensee SessionAllocate a NetLicensing floating-license session for a licensee and return the validation results with their cache TTL. Approval by default
  • WriteCreate BundleCreate a purchasable NetLicensing bundle from existing license templates. Approval by default
  • WriteCreate LicenseAssign a license from a license template to a licensee. Approval by default
  • WriteCreate LicenseeCreate a licensee under a product so licenses can be assigned and validated. Approval by default
  • WriteCreate Licenses From BundleCreate one or more licenses for a licensee from the license templates associated with a bundle. Approval by default
  • WriteCreate License TemplateCreate a license template under a product module using a supported license type. Approval by default
  • WriteCreate ProductCreate a NetLicensing product that can contain product modules and licensees. Approval by default
  • WriteCreate Product ModuleCreate a licensing-model-specific module under a NetLicensing product. Approval by default
  • WriteDelete ResourcePermanently delete a product, product module, license template, licensee, license, or bundle by number. Approval by default
  • WriteTransfer LicensesIrreversibly transfer all eligible licenses from a source licensee marked for transfer to a target licensee in the same product. Approval by default
  • WriteUpdate BundleUpdate selected bundle details or replace its complete set of license templates. Approval by default
  • WriteUpdate LicenseUpdate a license's identity/number, name, parent-feature relationship, status, timing, pricing, visibility, or quantity. Approval by default
  • WriteUpdate LicenseeUpdate selected status, identity, transfer, or non-secret custom properties of a licensee. Approval by default
  • WriteUpdate License TemplateUpdate selected pricing, visibility, limits, or license behavior on a license template. Approval by default
  • WriteUpdate ProductUpdate selected properties of an existing product; supplying discounts replaces the complete discount set, and an empty discounts list clears all discounts by sending one empty discount field. Approval by default
  • WriteUpdate Product ModuleUpdate selected properties and model-specific settings of a product module. Approval by default
  • WriteValidate LicenseeValidate a NetLicensing licensee's active licenses and return the validation results with their cache TTL. Approval by default

One prompt, start to finish

What a governed NetLicensing run looks like inside Luumen.

Questions

How does LuumenAI connect to NetLicensing?

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 NetLicensing on its own?

Read actions answer immediately. Anything that writes — check in licensee session, check out licensee session, create bundle, create license, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to NetLicensing — read or write, approved or declined — 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 NetLicensing to work with Luumen

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

Book a DemoDownload Luumen