Netlicensing Labs64 NetLicensing RESTful API

Name: Labs64 NetLicensing RESTful API
Brand: Labs64 NetLicensing RESTful API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage Registrybasic40 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Labs64 NetLicensing RESTful API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Labs64 NetLicensing RESTful API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Labs64 NetLicensing RESTful API.

Validate a license at application startup against a licensee number

Mint a new license from a license template for a specific licensee

Transfer licenses between licensees during account migrations

GET STARTED

Start building with Labs64 NetLicensing RESTful API

Explore with Jentic

View OpenAPI Document

Labs64 NetLicensing is a cloud-based licensing-as-a-service platform that lets software vendors create products, define license templates, issue and validate licenses, and bill licensees. The 40-endpoint REST API covers the full lifecycle: register products and product modules, mint licenses against templates, validate them at runtime, and reconcile transactions and payment methods. Use it to embed entitlement checks into desktop, server, mobile, IoT, or SaaS applications without building your own licensing backend.

Use Cases

Patterns agents use Labs64 NetLicensing RESTful API for, with concrete tasks.

★ Runtime License Validation

Call the validate endpoint at application startup to confirm a customer's license is active, within its time window, and authorised for the requested feature set. NetLicensing returns a structured validation result per product module so the application can degrade gracefully or block usage. Validation supports offline grace periods configured on the license template.

Call POST /licensee/{licenseeNumber}/validate with productNumber set to PROD-123 and return whether each module is valid and its expiry date.

Subscription License Issuance

When a customer completes checkout, mint a new license from a subscription license template against their licensee number. NetLicensing tracks the transaction, billing window, and renewal eligibility so the application can read entitlement state directly from the API rather than syncing it locally.

Create a new license for licensee LIC-456 from license template TPL-MONTHLY-PRO with start date today and confirm the license number returned.

License Transfer During Migration

When a customer reorganises accounts or sells a seat, move active licenses from the source licensee to the target licensee through the transfer endpoint. NetLicensing keeps an audit trail in the transaction log so the original purchase history is preserved.

Transfer all active licenses from licensee LIC-123 to licensee LIC-789 and return the resulting transaction number.

AI Agent Entitlement Manager

Let an AI agent answer support and billing questions like 'when does this customer's license expire?' or 'why is the validation failing?' by querying NetLicensing directly through Jentic. The agent fetches the licensee, the active licenses, and the most recent validation result without an engineer dropping into the admin console.

Given customer email alex@example.com, find the matching licensee, list active licenses with expiry dates, and explain why the most recent validation returned invalid.

Key Endpoints

40 endpoints — labs64 netlicensing is a cloud-based licensing-as-a-service platform that lets software vendors create products, define license templates, issue and validate licenses, and bill licensees.

METHOD

PATH

DESCRIPTION

POST

/licensee/{licenseeNumber}/validate

Validate a licensee's licenses at runtime

POST

/license

Create a new license

POST

/licensee/{licenseeNumber}/transfer

Transfer licenses between licensees

GET

/licensetemplate

List license templates

POST

/product

Create a product

GET

/transaction

List licensing transactions

POST

/licensee/{licenseeNumber}/validate

Validate a licensee's licenses at runtime

POST

/license

Create a new license

POST

/licensee/{licenseeNumber}/transfer

Transfer licenses between licensees

GET

/licensetemplate

List license templates

POST

/product

Create a product

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your NetLicensing username and password are stored encrypted in the Jentic vault. Agents receive scoped access — basic auth headers are constructed at execution time and never exposed to the agent context.

Intent-based discovery

Agents search by intent (e.g. 'validate a software license') and Jentic returns the matching NetLicensing operation with its parameter schema, so the agent calls the right /license, /licensee, or /validate endpoint without docs.

Time to first call

Direct NetLicensing integration: 2-4 days to wire auth, model the licensee and template flow, and add validation. Through Jentic: under 1 hour to search, load, and execute the first call.

FAQs

Specific to using Labs64 NetLicensing RESTful API through Jentic.

What authentication does the NetLicensing API use?

NetLicensing uses HTTP basic authentication with your NetLicensing username and password (or an API key as the password). Through Jentic those credentials sit in the encrypted vault and never enter the agent's prompt context.

Can I validate a license at runtime through the NetLicensing API?

Yes. POST /licensee/{licenseeNumber}/validate returns a per-product-module validation result you can call at application startup or on a heartbeat. The response indicates whether each module is valid and when it expires.

Can I issue a new license programmatically with the NetLicensing API?

Yes. POST /license with a licenseTemplateNumber and licenseeNumber creates a new license. The license inherits term, pricing, and feature settings from the chosen template.

What are the rate limits for the NetLicensing API?

Labs64 does not publish a fixed rate limit; throughput is governed by your NetLicensing plan. Validation traffic is the highest-volume case and is built to handle production application load.

How do I transfer licenses between customers through Jentic?

Run jentic.search('transfer software licenses between customers'), load the matching NetLicensing transfer operation, then execute against POST /licensee/{licenseeNumber}/transfer with the source and target licensee numbers. Jentic returns the resulting transaction record.

Does NetLicensing support feature, subscription, and rental licensing models?

Yes. Each product module is configured with one of NetLicensing's licensing models including Feature, TimeVolume, Subscription, Rental, FloatingMultiFeature, and PayPerUse. The API returns the model on each product module so applications can branch on it.

Netlicensing Labs64 NetLicensing RESTful API

Connect the Labs64 NetLicensing RESTful API to your agent

Capabilities

Start building with Labs64 NetLicensing RESTful API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs